Skip to content

Docs

Agents

Riley handles the project-management work around meetings, time and knowledge. Charlie reads a repository and proposes code. Both are off until two separate people say yes.

Where to find it: Settings → Agents for the org; Settings → My Agents for yourself.

What this section is about

An agent needs two consents, and they are ANDed. An admin makes the agent available to the organization; each person then switches it on for their own work. A fresh OS3 has every agent inert until both have happened, and nothing an agent does happens to somebody who has not opted in.

The master switch is the consent. The feature switches beneath it trim what the agent does — they are not each a separate opt-in, which is why a feature added later is covered by the consent you already gave rather than arriving as a dead switch nobody finds.

Agents cost money per token, metered and visible. They act as the person who asked, so an agent can never reach something you could not.

Important features to use

  1. 01Riley, around meetingsWrites the notes page, proposes knowledge-base updates, creates the tickets a call committed to, and logs an hour per attendee. Each of those is its own switch under Settings → My Agents, and the notes page itself is never suppressed — that is the record of the call, not an opinion about it.
  2. 02Riley, in conversationOn mobile you can ask Riley what is on today, log time, create and update tickets, and write knowledge pages. It acts as you, through the same rules the web app enforces, and every action it takes is reported back.
  3. 03The end-of-day check-inA conversation for closing out: it sweeps your calendar for meetings nothing recorded, tells you what is logged and what is waiting, and offers the areas that need attention rather than marching you through them.
  4. 04Charlie, per ticketAssigning the engineer agent to a ticket is what starts a run, and the ticket carries how far it may go unattended: plan only, push to a dev branch, or promote to production. Production additionally requires an admin. A project has to have a repository attached before the agent can be assigned at all.
  5. 05Budgets are real moneyEach agent has its own API key and per-ticket and monthly caps, so spend lands somewhere an admin can see and limit. A cap stops new runs rather than interrupting one mid-flight, so it can be overshot by at most one run.
  6. 06Everything proposed about a document waitsTickets and hours are created for real, because a ticket has nothing to overwrite and an hour lands in a review queue. A knowledge-base change is held outside the page until a person approves it, because approving one overwrites something somebody wrote.

Common questions

Nothing is happening. Did I miss a step?
Almost certainly the second switch. Check Settings → Agents (an admin has made the agent available) and then Settings → My Agents (you have switched it on for yourself). Both default to off.
If I switch Riley off for myself, do I lose my settings?
No. The per-person feature switches survive the master switch going off and on again, and they survive the org switch doing the same.
Can an admin switch an agent off for one person?
No — that is the person's own control. An admin who needs an agent stopped switches it off for the organization, which is a different thing with a different meaning.
What does an agent cost?
Per token, by the model it runs. Settings → Cost shows what has been spent, broken down per agent where each agent has its own key.
Can Charlie delete things or touch production on its own?
No. It has no delete, and production promotion needs both the project to permit it and an admin to grant it on the specific ticket.