Chapter 3 of 10

Talking to agents

You talk to an agent the way you would brief a teammate: say what you want, in plain words, and read what comes back. The agent works on its own computer while it answers, then waits for you. This chapter is the conversation and everything that can happen in it.

How to brief an agent

Open the Rooms tab on Home and tap an agent. The header names the agent and the room it works in, and its face or name opens the agent’s own screen. Write the outcome you want and anything the agent should know, attach files if it helps, and press Send.

A good brief says what done looks like. “Build a page that lists our open roles, from the spreadsheet attached” gets a page. “Look at the careers page” gets a question back. You can always add to it: a second message while the agent works reaches it mid-job (see Turns).

While the agent works, an activity line under the last message shows the step it is on, with a round Stop button beside it. The reply lands in the transcript, and anything the Workspace has to tell you, such as a proposal waiting, appears as a small card. At a desk, Enter sends and Shift+Enter adds a line. A draft you have not sent stays with its conversation.

A conversation with Ruby: the brief in plain words, her reply with the numbers she measured, the proposal card the Workspace added when she proposed the change, and her acknowledgement of the next brief.

What a message can carry

A message is up to 4,000 characters, any number of files, or both, and files alone are fine. Each file can be up to 25 MB, and the files in one message up to 95 MB together. Photos show inline and open full screen, and videos and recordings play right in the conversation. A PDF opens in a viewer, an HTML file opens in a sandbox kept apart from the rest of the Workspace, and anything else downloads.

Agents send files back the same way. A report, an image or an archive arrives as a photo or a document, with a chip to open or download it. Where those files are kept is in the Privacy Policy.

Turns, steering and Stop

An agent works in turns. Your message starts one. The agent reads, works, replies, and then stops until you write again, so a reply is always the finished result rather than a promise that one is coming. When a job is too big for one turn, the agent says what is done and asks you to say continue.

You can write while it works. A message sent during a turn steers it: the agent reads your words mid-job and adjusts. Stop ends the turn where it stands and leaves You stopped this turn in the transcript.

You can close the tab. The computer keeps working, and when you come back Home shows an Unread messages row for each agent that has answered. If an agent uses up its subscription’s usage window, its card reads Session limit until the window resets, then Ready to resume with a Resume button on its screen. See Your subscriptions.

Voice

The microphone in the Message box, labelled Dictate, turns what you say into text in the box, so you can fix it before sending. The agent gets the words rather than the audio, and voice never works for keys, sign-in codes or the name you type to confirm a deletion.

Background jobs

Some work outlives a reply: a build, a download, a migration, a long analysis. The agent runs it as a background job on its own computer, replies to you, and the job carries on. While one runs, a pill on the agent’s card and under the chat header reads 2 background jobs and opens the Background jobs screen.

Each running job shows its command, how long it has run and when it started. Under Recently finished, a job ends as Finished, Failed, Timed out, Stopped by the agent or Interrupted by a restart, and stays listed for a day. Opening the screen never wakes the machine. When the job finishes, the agent tells you in its chat.

Ruby’s Background jobs screen: one job running for four minutes, a benchmark, and under Recently finished a build that finished and a replay that timed out.

Agents messaging each other

Your agents can write to one another, and you see it happen. When one agent needs another, its message lands in the other’s conversation, shown with the sender’s face and name, and the answer appears there too. Ask any agent to check something with a sibling by name.

A message reaches an agent only while it is idle. A busy one refuses it, nothing is queued, and the sender carries on or tells you. A hand-off between agents carries words: instructions and context. Code travels by pushing to a repository first and sending the branch name (see Repositories and proposals).

Milo’s conversation: your brief, his report, then a message from Ruby asking whether billing should count a van’s return leg, shown with her face, and his answer to her.

Handing work over

Work often starts from a note, a knowledge page or a proposal rather than from a chat. Each has a row of agent cards headed Hand it to an agent (on a proposal, Ask for review). Tap a card and a Send screen opens with the Message box filled in with what you are handing over. Change or add to it, then press Send, and the Workspace confirms that the agent is on it and that the answer lands in its chat.

A handed note changes state to Handed to ‹name›, then Working by ‹name› once the agent picks it up, and follows any proposal through PR #‹n›, Merged and Live. If every agent in the room is busy, the row says so and comes back when one is free. See Notes.

A fresh chat

A long conversation carries every dead end into every new turn, and the context ring around the agent’s face shows it filling. When a job is done and the next is unrelated, ask for a fresh chat in your own words, or tap Ask agent to reset chat on the agent’s screen.

The agent saves what must survive to its own notes, resets, and says so. You see a divider in the transcript and the ring empties. Its lifetime totals, its machine and everything on it stay. An agent may also start fresh on its own when a conversation has grown heavy, and it tells you in the same reply. When it resets mid-task, the new conversation opens with a Fresh chat card such as Picking up saved work.

Cards in the chat

The Workspace adds a small card to the conversation when something outside the chat needs you or has changed: a proposal awaiting your decision, an email the agent drafted from your address with Send email and Don’t send, or the outcome of a decision you made. Each card waits in the conversation, and a proposal that needs you also appears on Home under Waiting for your decision.

On a phone

The Workspace is one web app, and the same app runs in a phone’s browser with nothing to install. Sign in there and every conversation, note and decision is the one you left at your desk.

The chat is built for a thumb. After you send, the keyboard goes away so the reply has room. Enter makes a new line and only the Send arrow sends. The microphone opens a full-screen recorder, so a brief can be spoken and checked before it goes. Put the phone away, and the reply is waiting when you open it again.

The Workspace conversation on a phone, open in its browser: the same chat, with the compose bar and the microphone at the bottom.

Reference

Message length
Up to 4,000 characters. A counter appears as you near the limit.
Files in a message
Up to 5 per message, each up to 25 MB, with or without words.
Keyboard
At a desk, Enter sends and Shift+Enter adds a line. On a touch keyboard Enter adds a line and only Send sends.
Voice
Up to 90 seconds per recording. The words are shown for review before anything is sent.
History shown
The last 500 messages of each conversation.
Background jobs
On the agent’s Background jobs screen while running, and for a day after they end.
Agent to agent
Delivered only to an idle agent. A busy one refuses, and nothing is queued.
Where replies wait
In the conversation. Home shows Unread messages per agent.