Skip to Content

Chat

Chat is a direct line to a coding agent, outside the pipeline. Use it to explore a codebase, gather information before writing a task, or make a quick surgical change that doesn’t warrant the full task workflow.

Start one from Chats in the sidebar with New chat.

Scope and model

Each chat picks a provider and optionally a model. You can also scope the conversation:

  • Project: the agent works in that project’s directory. Without a project, it can see all of the workspace’s projects.
  • Task, and optionally a variant: the agent gets the task’s context, useful for asking about work in flight or nudging a variant along.

What chat can do

Chat agents have the same access as pipeline agents: they read your code, run tools, and can edit files directly. You’ll see responses stream in as they’re produced, including each tool call the agent makes. Because chat edits land wherever the chat is scoped, treat it like handing your keyboard to an agent: great for quick changes, while bigger work belongs in a task where it gets a branch, review, and a diff.

Sessions

Chats persist. Each conversation keeps its full history, continues across app restarts, and keeps running server-side even if you navigate away mid-response. Have as many concurrent chats as you like; rename or delete them from the sidebar.

Last updated on