Working in a task¶

A task is a conversation with one agent in one sandbox. This page covers what you can do once it is running.

The composer¶

Control	What it does
Repository and branch	Where the agent starts, and what the pull request targets. Start from scratch works without a repository — see Start from scratch
Agent	Which coding agent does the work. It stays the same for the whole conversation
Model and reasoning	What drives the agent. You can change them on every turn — see Agents and models
+ → File	Attach files. The agent finds them under `/uploads`, outside the repository, so they are never committed. Up to 50 files, 5 MB each and 20 MB per message
+ → Goal	Keep the agent working until a condition is met — see Goals
+ → Skills, MCP servers, SSH servers	Reusable instructions, tools and your own servers for this conversation — see Tools, skills and memory
+ → Plugins	Agent plugins to install when the sandbox starts. New tasks only — see Plugins
+ → Environment	Which saved environment prepares the workspace. New tasks on a repository only — see Environments

Rewrite prompt expands your draft with the selected model before you send it. With Ask clarification questions first, the model asks a few questions before it rewrites. The result stays in the editor for you to review, and the call counts toward your daily quota.

Follow-ups¶

A follow-up goes to the same agent session in the same sandbox, so the agent keeps its conversation history, the files it changed and the packages it installed. The sandbox is stopped after 30 minutes without activity and started again when you continue.

Messages you send while the agent is working wait in a queue and are sent one by one after the current turn. You can edit or delete a queued message until it is sent. With Claude Code and Codex, Steer now (⌘/Ctrl+Enter), or Add to this turn on a queued message, hands the message to the running turn instead; the agent reads it before its next tool call. A message with attached files always goes as a turn of its own.

The model and reasoning level can change on every turn. The control beside the message box starts on what the last turn used, so a conversation can open on a fast model and move to a larger one where the work turns out to be hard.

Questions and plan approvals¶

When an agent asks you a question, a dialog opens and the turn waits. Choose an option or write your own answer. Answer later closes the dialog and leaves the question waiting; Skip declines it. Claude Code’s plan approval uses the same dialog: Approve plan lets it start implementing, and Skip asks it to keep planning.

Stopping a turn¶

Stop, or Escape while the focus is not in a text field, interrupts the agent. Its changes stay in the workspace, and a follow-up continues from them. Queued messages pause; choose Continue to send them. Stopping does not recall a pull request that is already being published.

Goals¶

A goal keeps the agent working across turns until a condition is met. Type /goal followed by what “done” means, for example /goal make the unit tests pass, or choose + → Goal. After each round, the platform starts the next one on its own until the agent reports the goal complete.

The band above the message box shows the goal and how many rounds have run. Pause stops it after the round in flight; use Stop to interrupt that round too. Resume, Edit goal and Clear goal do what they say. A goal also pauses when the agent needs your input, a round fails or is stopped, your quota runs out, or the conversation is archived or forked; the band says why. Every round counts toward your daily quota.

Forks and side chats¶

Action	Where	What you get
Fork from here	On the last answer of a finished turn, or Fork in the task’s menu	A new chat with the history up to that turn
Edit & rewind	On one of your own messages	A fork from just before that message, with the message in the composer, ready to change and send
Side Chat	In the workspace pane	A second chat beside the main one, for questions on the side. It waits while the main conversation runs

A fork shares the original’s workspace — the same files in the same sandbox — and can run at the same time, with its own agent session. Changes made in one are visible in the other, and rewinding does not undo files. A fork shares the original’s branch and pull request as well.

Review and Watch PR¶

Once a conversation has a pull request, two more actions appear beside it:

Review starts an independent code-review agent in a workspace tab. It reviews every change since the conversation’s starting point, including changes not yet in the pull request, and reports findings without editing files. Fix issues then asks it to fix what it found. Selecting Review again reopens the same review. A review needs the conversation’s agent session, so it cannot start from an archived conversation or one that lost its session.
Watch PR and merge starts a follow-up in which the agent watches the pull request’s checks and reviews, fixes failures and feedback, and merges once the pull request meets its required checks and reviews. It can start only while no conversation sharing the workspace is running or has queued messages. The agent needs a GitHub MCP connection that can write, to read checks and merge; a personal access token needs read and write access to Contents and Pull requests. Your repository’s branch protection decides what may merge without a person. If the agent makes fixes, the turn ends so you can Update PR; select Watch PR and merge again to keep watching. Watching also ends with the turn’s one-hour limit.

The workspace pane¶

Open the workspace from the task header, or with ⌘/Ctrl+J:

Git shows the changes the agent has made.
Terminal opens a shell in the sandbox.
Files browses the sandbox’s current files — see Files.
Environment shows how the workspace was prepared and runs your saved actions — see Environments.
Side Chat and Review tabs appear when you open them.

Files¶

Files shows the repository as it is in the sandbox now, and Changes lists the files the agent changed. The pane is read-only; ask the agent to change files.

Open file or folder by path opens a path such as src/app.ts without expanding every folder above it. Workspace root goes back to the whole tree.
Copy path and Copy contents copy the selected file’s path or text, and Download file saves it. A file too large to preview cannot be copied or downloaded here. HTML and SVG files are shown as text, never run.
Try again retries a folder or file that failed to load, and Refresh files reloads what is open.

Notifications¶

My Settings → Notifications turns on browser notifications for agent questions and finished turns, across all your chats; you can choose each kind separately. Clicking a notification opens that turn. They arrive only while the app is open in your browser.

Archive and delete¶

From the sidebar, Archive hides a task without deleting it; it does not stop a running turn. Archived in the sidebar lists archived tasks, and Unarchive brings one back.

Permanently delete removes a task for good and stops it if it is running. Forks and branches or pull requests that were already pushed are not affected. A workspace that other conversations share is kept until the last of them is deleted.

The task’s menu also has Rename, Pin and Download session log.