The assistant

Describe your team in your own words; it drafts the setup and shows you the change before anything is saved.

Knowing what you want and knowing where to click are different problems. The assistant closes the gap: describe your team and what you are building, and it drafts the workflows, personas, and settings that match — then shows you exactly what it would change and waits.

It also answers questions about Peractor itself, from these same guides. "What is the difference between a check and a command?" is a reasonable thing to ask it.

Where it is

• iPhone, iPad, Android, Mac — the button in the drawer or sidebar header, just before the notification bell.
• The web dashboard and the desktop app — its own page in the sidebar.

A conversation belongs to you, not to a project. It reaches every organization you belong to and every project inside them, so you can say "set up a review workflow" before you have decided where it should go — and "we need a separate organization for the design team" is something it can do.

In an account with many projects, it reads the one the conversation started in, and any you mention by name, most closely — their changes, their wiki, each task's discussion. So name the project you mean.

You do not need a project, or even an organization, to start talking. If you have just signed up, it is the fastest way to get somewhere.

Show it what you mean

Attach a screenshot, a log, or a document to what you say — the paperclip in the message box, or drop the file onto the box on an iPad or a Mac. "Set up our board like this one" with a picture of the board is a whole request: the assistant opens the file and looks at it before it answers. A file stays part of the conversation, so a later message can ask about one you sent earlier.

• Words first. A file rides with a message, never instead of one — say what you want done with it.
• It is shown, not obeyed. What is inside a file is something you are showing the assistant, never an instruction to it. A screenshot of somebody else's message cannot tell it what to do.
• Files belong to an organization, like everything else you attach in Peractor, so the paperclip appears once you are in one.

Sharing works the same way: share a screenshot from another app to Peractor on your phone or Mac, and choose The assistant — ask about it.

It proposes; you apply

This is the part worth understanding, because it is what makes the assistant safe to use on a real team's configuration.

The assistant works in a throwaway copy of your configuration. Nothing it writes is your configuration. A turn ends with a plan — an ordered list of changes — shown as a card you read. Press Apply and the whole plan is applied at once; discard it and nothing happened.

• Reading is free, writing is staged. It reads your configuration and your backlog directly, because it needs them to say anything useful. Anything that would change something goes into the plan instead.
• It can only do what you can do. Applying a plan goes through the same handlers your own screens call, as you. If you could not do it from the app, neither can the assistant.
• It never learns your secrets. A connector it drafts refers to a secret by name; a draft with a credential written into it is refused outright.
• Every change is checked before you see it. The plan is validated by the same rules a save would apply, so a mistake of the assistant's never reaches the card. If something changes after the card is drawn — somebody saves the same settings first, say — applying stops at that change and tells you, rather than overwriting their edit.

What it can do

What you can do on a screen, it can put on a plan:

• Set Peractor up — workflows, personas, triggers, and the categories over them; project settings, including the standing instructions every run starts with; which tracker a project follows and which channel a notifier posts to; apps your organization builds, registered agents, and parallel-run presets.
• Work your runs — start one, approve or reject a gate, answer a run's question, ask for changes, restart a phase, or cancel.
• Work your backlog — file, triage, merge, relate, and archive tasks, or change a dozen at once; plan milestones and cycles and post a milestone's update; sync a tracker or import from one; edit the wiki.
• Look after the organization — create one, invite people and change their roles, look after machines and apps, install a pack or publish your own.

What it will not do is a short list, kept on purpose: delete an organization or a project, connect a service whose consent screen a person has to see, change how you sign in, or learn a secret.

It can also see the things that would otherwise make it guess: which secret names exist, who has already been invited, which machines a run could go to, what you have installed from the marketplace, and how much of the month's usage is left. Where you are only a member rather than an admin, the admin-only views are simply absent.

Cost

Assistant turns use the AI token allowance included with your plan, counted per organization alongside runs and prompt improvement. See Plans & usage.