Chat

Chat is the page you will spend most of your time on: one conversation with one of your agents, and a preview pane that opens beside it when there is something to look at. It is a working surface rather than a message box: everything the agent does while it answers, the files it reads, the pages it builds, the permission it asks for, appears in the same thread.

The composer

The box at the bottom is the composer. Type, press Enter, and the reply streams in as it is written.

A split chip in its control row shows which model the chat is running on. Click the name to open the model picker, and the level beside it to change how hard the model thinks, on models that allow that. Until you set one, the level shown is the one the route gives that model, tagged route; your own choice sticks to the chat and wins until you switch to a different model, which starts it afresh on that model's route level. Beside the chip a ring shows how full the conversation has become; clicking it offers to compact the thread or start a fresh one. Conversations explains when to bother.

Slash commands live here too. Type / and a short list appears: /model, /compact, /context, /usage, /status and more.

Drafts are kept per chat, so you can walk away and your unsent text is still waiting tomorrow.

Sending more than words

Files of any kind go in through the paperclip, a drag onto the chat, a paste, or a tile dragged from the preview pane. Thumbnails appear above the input with progress and a cancel, and an upload interrupted by a reload resumes. Attachments are kept in the agent's workspace, so size is never the reason a message fails to send. Paste a long block of text and it becomes a Pasted text card on the message instead of filling the box.

The microphone records a voice message, transcribed on arrival and sent with a player and its transcript. The telephone beside it starts a live voice call with the same agent: that one is still experimental, and says so the first time you use it. Speak back has replies read aloud. All three are covered in Voice.

Send something that looks like a password or a key and Player One stops you first, pointing at the Vault instead.

While it is working

A Stop button appears while a reply runs. Send becomes Add to queue, and queued messages stack in a panel above the composer. A short one usually reaches the reply already running rather than waiting its turn, so a correction lands while it still matters; the row tells you which.

One line at the foot of the reply says what the agent is doing at that moment: a spinner, a verb and the thing it is working on, such as reading a file, running a command or using a skill. Each new step slides up into place as the last one leaves, and the thing being named is coloured by what it is, so a skill, a tool, a file, a command and a web address are told apart at a glance. Before there is anything to show it says Thinking, rephrasing itself now and then so you can see it is still alive, and where the model streams its reasoning the line carries the latest sentence of it instead. If the connection to your installation drops mid-reply the line says so, and picks the run back up when it returns.

Agents can write their own notes onto that line, so a long piece of work can tell you what it is up to in its own words without cluttering the answer. The line goes when the answer starts to arrive: any prose after that is the reply itself.

Click the line, and What's happening opens: every step so far, filling as they land. It keeps its place while a step is on screen and shows what each one was given and what it returned, with the agent's thinking quoted in full. Once the reply is finished the same panel is What happened, reached from the steps chevron in the footer, so you can go back over a reply of an hour ago and see exactly what was run and in what order. A reply that carries on after its text has landed, waiting on a command, says In progress rather than leaving you guessing.

Under each reply is a footer naming the model that produced it and what the turn used, explained in Tokens, cost and caching. Where a chat changed model part way down, a labelled divider marks the spot. Where one answer took the agent several turns, a light rule separates them inside the one reply.

Not everything in the thread is text. An agent that needs an answer puts a small form in the conversation: a choice, a few fields, or a masked box for a password that goes to the Vault without passing through the agent. When it needs permission, to run a command or open something secure, an approval card appears with the decision buttons on it, and deciding it lets that conversation continue. A command card offers Once, Always and No; Stay in control says what each one keeps. Work handed to a helper shows as a face in a row beside the composer, one click to read, and a message from another of your agents arrives as its own card with the sender named.

The preview pane

When an agent makes something worth looking at, a document, a page, a chart, it opens on the right and refreshes as the work changes. Press Preview in the chat header to open the pane yourself, with your files to pick from. On a phone it is a Preview tab beside the chat. See The preview pane.

How it fits

Every chat is with one agent, and the scope switcher above the chat list decides who a new one starts with: see Agents. Each chat sits in a project, which is what your folders, your search and your Trash are scoped by: see Projects.

What a conversation teaches Player One need not stay inside it: your agents save what is worth keeping, so something you explained in March is still known in September. See Memory.

The same agent, with the same memory and the same tools, also answers on WhatsApp, Telegram, Slack and email: see Talk to it.

Where it lives

New chat at the top of the sidebar (/) opens a blank conversation with whichever agent the sidebar is pointed at, its name on the row. Below the navigation your chats are listed with folders first, then pinned chats, then the rest by day. A chat's helpers, the chats its agents started for it, sit around its row when you open it, and the cog at the top of the list chooses which kinds of chat it shows: Conversations has the detail.

The chat's own controls float at the top left of the conversation: an i button for its details and a rename, and a dots menu for fork, pin, Hide from sidebar and delete.