Chatting with Your Agent

Each project has one conversation with the agent. Open a project and start typing — that's it.

How it works

• Each message you send can trigger the agent to call tools — searching the web, reading files, writing notes, creating tasks, or whatever else you've enabled in the project.
• The agent can chain multiple tool calls together to complete a request. You'll see each step as it happens.
• Conversations are persistent — the agent remembers what you said and did in the project, across sessions. When a conversation gets long it's automatically summarized so older context stays available without slowing things down.
• Responses are resilient — if you close the tab, put your laptop to sleep, or lose connection mid-response, the agent keeps working. Reopen the chat and you'll rejoin the live response (or find it finished and waiting). Only the Stop button cancels a run.

Getting good results

• Be concrete. "Summarize today's GitHub notifications and post an update" beats "check GitHub."
• Add project instructions for things that apply every time (see Projects). You only have to say them once.
• Use skills when you have a procedure the agent should follow — a multi-step workflow, a style guide, a specific prompt template. See Skills.
• Pick the right model for what you're doing. More capable models cost more but do better on harder reasoning. See AI Models.

Queueing messages

You don't have to wait for the agent to finish before sending your next message. If you send while it's still responding, the message is queued — it shows up below the response with a "Queued" label and sends automatically, in order, as soon as the agent finishes.

• Queue as many messages as you like; they send one at a time.
• Changed your mind? Click the X next to a queued message to cancel it before it sends.
• Queued messages live in your browser tab — closing the tab discards any that haven't sent yet.

Stopping an in-flight response

If the agent starts doing something you didn't want, use the Stop button in the chat. It interrupts the current run immediately. If you have messages queued, the next one sends once the run stops — cancel them first if you don't want that.

Clearing history

You can clear a conversation's history from the project's chat menu. Useful if you want to start fresh or if the agent's gone off on a tangent.

Task conversations

When you open a task, it has its own chat — separate from the main project chat, but in the same project. It's a discussion thread scoped to that to-do: iterate with the agent on what the task needs, and it can act right there. Tasks don't run on their own — for work that should happen on a schedule, the agent sets up a background agent. See Tasks.