Getting Started

This is the path an admin takes from an empty account to a loop that a user can run. Only the people of your account (owners, members and viewers) sign in to Reactor. The people your loops serve never do — they meet a loop on your page or in your product.

Try one first

This is a loop that plutonium.io runs on these docs. Ask it a question: it answers from these pages and names the page it used. A loop you build meets your users the same way.

Not sure what to build? What Loops Are For lists the jobs a business hands a loop, with a person in the conversation or with nobody at all.

Reactor is not open for sign-up yet. Join the waitlist on the home page: we add people by hand, and we email you when your account is ready. You are its owner, and its wallet starts with $5.00 of starter credit. Then sign in to the console with Google, at the address we wrote to. The console opens on Home: your credit, what needs you, what is running, and this month against its budgets, under a line that names the account and your role. A new account’s owner sees Getting started first: try a demo loop, set up your first loop, then publish it. Each step ticks itself when it is done, and Hide puts the list away. Choose a demo offers four of the demos on our home page: sort a support message, qualify a lead, meeting notes to actions, and file an expense. Copy it as a draft puts that demo’s loop, its collection and its page into your account as drafts, named “Demo: …”. A copy speaks for Larkspur, an example software company: change its prompt to speak for your own. Nothing runs or spends until you try it: Home then says it is in your account, and Try it in Chat opens a new chat with it. A press first reads what your account holds and writes only what is missing, so copying the same demo again keeps the copy you already have. Describe it to LoopAssistant opens My conversations on LoopAssistant, a loop plutonium.io owns that helps you write your own. After your first publish, Home shows Your loop is live, with the code to put it on your site.

Each screen shows its title. Press the ? beside a title to read what that screen is for. If a screen fails to draw, it shows “Something went wrong on this screen. Reload to try again.” and a Reload button in its place. The menu and every other screen keep working.

2. Check the wallet

Nothing runs until the account’s wallet holds money: every call a run makes is reserved against it first. A new account starts with its $5.00 of starter credit. Adding money by card opens soon; until then, we add credit to your account. Wallet & budgets shows the wallet, what each loop has spent this month and the caps you set.

3. Describe the loop to LoopAssistant

Tell LoopAssistant what the loop is for. It interviews you and proposes the loop as a record you read and edit before anything runs — its instructions, the tools it may call, what it must produce, who may use it and what a run may cost. The model that drafts the loop never publishes it by itself: it can ask, and your press on its card publishes.

You can also start a loop yourself: Loops → New loop.

4. Know what a loop is built from

A loop does its work through parts you can see and manage on their own pages, in the Build group of the console:

Agents — the workers a loop runs: their instructions, the tools they may call, their model and their role. The console lists plutonium.io’s own agents beside the ones you create. Publishing a loop pins the agent version it uses.
Tools — your own HTTP endpoints. Install one once from a form, and several loops can declare it. A header secret you give it is stored and never shown again.
Collections — the records your loops write, collection by collection.
Indexes — what your loops can search: a crawl of a website, files you upload, or one of your collections. A loop’s page lists the indexes its runs may search, and an index that a published loop uses cannot be deleted.

5. Test it, then publish

A loop is written as a draft, and a draft never serves a user. Try it from My conversations: a new conversation lets you pick the loop and the version it runs in, draft included. If the loop declares test conversations, the version publishes only after they have run against it. My conversations lists only the conversations you started. Those of other members, and runs that users, keys and triggers start, are on All runs.

Then publish the version. What you published is what runs, and it does not change afterwards: the next change is the next version. Publishing gives the loop its public id (pl_…), which is how the world outside the console names it.

6. Choose where it runs

A loop reaches users only through the deliveries it declares, and only from the web origins it allows. On Loops, a published loop’s Keys tab shows its public id, and what each delivery needs from you:

Embed — a chat on your own web page. For a loop that declares it, the tab is called On your site: it lists the sites the chat can load on, adds one, and shows the snippet to paste.
API — your own server or interface calls the run API. Mint a key on the Keys tab with the create_runs scope; the key is shown once. See Runs in the API reference.

Keys are for owners. A key can do only what its scopes allow, and only within what the loop declares.

7. Watch it run

All runs shows every run live: who it was for, what it did, what it cost, and why it ended. You can stop any run from there. Metrics shows how each loop is doing across its versions, or for one version you choose: its runs, how they ended, what they cost and how long people waited.

Ask the Assistant

The Assistant answers questions about the console from these docs. It is not a general assistant: to a question that is not about Reactor, it answers “The docs do not cover that. I can help with Reactor.” Under each answer, Sources links to each page its search found. On a desktop it is a panel at the right of every screen; on a phone it is a sheet that opens over the bottom 60% of the screen. Press or drag its handle up to make it full screen, and drag it down to make it smaller or to hide it. It is open on Home. On any other screen, press Assistant: at the bottom right on a desktop, and at the right of the bar under the header on a phone. Hide closes it, and the console remembers that choice in this browser. On My conversations the panel folds to its Assistant button, so the screen has one box; press the button to open it there too. Each box says who answers: the chat’s box reads Message LoopAssistant (the loop you are talking to), and the panel’s reads Ask the Assistant about publishing, roles, pages….

When the panel leaves too little room for a list and the item it opens side by side, the screen shows one at a time, as on a phone: press an item to open it, and the link above it (‹ Loops, ‹ Chats) returns to the list. Hide the Assistant to see both again.

Besides answering, it can do three things:

Take you to a screen. “Take me to Schedules” opens Schedules, and the Assistant stays open.
Point at a control. “Where is the publish button?” opens the screen and outlines the control for a few seconds. If the control is not on the screen now (Publish shows only on a loop that has a draft), it tells you what to do first.
Hand you to LoopAssistant. “I want a loop that qualifies leads” shows a card with a short brief of the loop you asked for. Press Send this brief to LoopAssistant, and LoopAssistant opens in a new tab of the panel with the brief sent as your first message, and starts work. The screen behind the panel does not change. Not now sends nothing. To change the brief first, write in Note to the assistant and press Reply: the Assistant reads your note, and nothing is sent to LoopAssistant. A note also goes with Not now, so the Assistant knows why. An agent you ask for goes to AgentAssistant the same way.

Each hand-off is a tab beside the Assistant tab, and the Assistant keeps its own conversation there. Answer LoopAssistant in its tab, or press Open in Chat to open the conversation in My conversations. Closing a tab with its × does not stop the conversation: it stays in My conversations. The tabs stay while you move between screens and when you reload the page, until you close the browser tab.

The Assistant reads nothing in your account: it knows these docs and where the console’s controls are. plutonium.io pays for its runs. Each member can start 60 conversations with it a day and send it 60 messages an hour.