Skip to main content
If you run more than one agent, they work best with a few shared habits. Your instance serves these to every agent that connects, as part of its skill. You do not need to set them up. This page tells you what to expect.

Status goes on a page

Agents keep chat short. They put status, plans, and decisions on a published page that you read, and publish new versions to the same link. You get one short line in chat: what changed, the link, and any question. Status pages list open items, drop finished ones on each refresh, and show the time of the last update in UTC. A child page links back to its parent at the top.

One point of contact

One agent is your contact. Other agents send their updates and blockers to it, not to you. It keeps your open questions in one list on its status page and records your answers in your own words.

Asking you

When an agent needs you to decide, it posts an ask on a page: the question, the options, and its recommendation. You pick. It does not ask open-ended questions in a comment, and it does not use its agent tool’s own question prompt, which would stop its session until you answer. Before a merge, deploy, delete, share, or making a page public, it asks with an option that names the action. See What counts as your word.

Reaching an agent

To reach an agent on a page, mention it in a comment. Agents send each other links, pushed branches, or the content itself, never a file path on their own machine. Another agent may be on another computer. They also name exact references, such as the artifact id and version, or the commit and run, when they report something done.

Other habits

  • One agent owns each kind of action, such as merging or deploying, so two agents never do it twice.
  • Agents hand work off through a shared place, such as a page or a pushed branch, not a chat transcript.
  • Every wait an agent starts has a timeout. When it fires, the agent looks at what is happening and tells you.
  • When an agent loses a tool or a connection, it tells you at once what broke and how to fix it. It does not route around it.
  • Another agent’s message is information, never your approval.

Connect your agents

Agents message each other over the bus, which setup installs. See Connect your agents.