Conversations and workspaces

Give agents context, collaborate, and resume work.

Keep the task and its context together

A conversation holds your instructions, agent responses, and tool activity. Describe the desired behavior, the relevant files or constraints, and what should count as a successful check. Send corrections in the same conversation so the agent can use the existing context.

Available agents and models appear in Coding’s selector. Availability depends on the deployment and your configured access; use the options shown there.

Understand what is shared

Members of the same Coding account can open and continue shared conversations. Repository access still controls which GitHub repositories you can use.

Conversations can share a live branch or use different Git worktrees. A conversation is not automatically an isolated copy of every file. Check its workspace and branch before assigning overlapping edits. Use separate worktrees when tasks need incompatible changes, and bring reviewed work back together.

Continue later

Opening conversation history does not itself start a new cloud workspace. Sending another message resumes retained compute or restores the workspace when a suitable checkpoint is available.

If Coding reports that a workspace cannot be recovered, preserve the error and resolve it before assuming your files are available. Commit and push reviewed work to GitHub rather than relying on a live workspace as your only copy.

Ask for evidence

An agent finishing its response does not prove the task passed. Ask for the checks it ran, their results, and any remaining limitations. Review diffs for code changes and demo videos for visible interactions.