Chat Tour

Say what you want, and the studio does it. Chat is how you direct Circuitry in plain language — a conversation that can see your documents, act on your selection, and drive coding agents across your whole project. Every other surface in the studio is something you shape with your hands; chat is where you shape things with intent. Pair it with a code file and the agent sees what you're looking at. Point it at a diagram and it builds what you sketched. Hand it to a coding-agent CLI and it becomes mission control for work happening on your machine.

One surface, three ways to talk

The icon at the left of the chat's header tells you which conversation you're in:

• Agent mode — the full studio agent, with tools. The icon glows blue when the agent's tool connection is live, emerald otherwise.
• Plain chat — a straight conversation with the model, no tools.
• CLI mode — the tab becomes an interactive terminal running a coding agent (Claude Code, Gemini CLI, or Codex CLI) with your project as its workspace.

Chats linked to a chat node in a workflow show a Synced badge here — the conversation and the node share one history.

A tour of the controls

Header toolbar

• New chat — start a fresh session (shown on standalone plain chats).
• Model picker — a dropdown showing the current model. In agent mode, each row lists the model name with its provider badge and a check on the active one. In CLI mode, the same dropdown switches between installed coding-agent CLIs — Claude Code, Gemini CLI, and Codex CLI — with an amber "not installed" flag on any that aren't available.
• Switch to CLI / Switch to Agent — flip the tab between agent chat and an interactive coding-agent terminal. Appears when you have a project folder open and a Circuitry Server connection.
• Clear chat — wipe the conversation (disabled when there's nothing to clear, or in CLI mode).

The composer

The message box at the bottom, plus a control row underneath it:

• Send — send the typed message; ⏎ sends too. Disabled while a turn is running or when there's nothing to send.
• Stop — while the agent is working, a small square stop button appears next to the Working… indicator; click it to abort the turn in flight.
• Permission mode chip — on agent chats, a chip at the left of the control row cycles through four modes with ⇧⇥ (or a click):
  • ▸ auto — the agent runs tools freely.
  • ? ask — approve each change before it happens.
  • ✓ accept — also auto-accept code edits.
  • ☰ plan — read-only; the agent plans but touches nothing.
• effort — on reasoning-capable models, a per-chat reasoning-effort selector (auto, off, minimal, low, medium, high, max). You can also type /reasoning <level> in the chat.
• model — in CLI mode, a per-chat choice of which model the coding-agent CLI runs with (CLI default, Sonnet, Opus, Haiku, or Fable).
• Remove attachment — when images or files are staged, thumbnails appear in a row above the composer; the ✕ on each one removes it before sending.

Keyboard

Shortcuts use ⌘ on Mac (Ctrl on Windows/Linux).

Cmd + and Cmd − zoom the chat text in and out while the chat panel has focus.

Works with the rest of the studio

• Agent Chat in Split-Screen — pair a chat with a code file or workflow; the agent sees your file, selection, and containing function, and its edits land as reviewable diff hunks.
• The Coding Agent — what the studio agent can do across your project.
• Circuitry as an Agentic IDE — the whole loop: plan visually, direct in chat, inspect in a real IDE.
• The Smart Whiteboard — when intent is easier to draw than to type, sketch it and let the agent read the board.
• Workflows Overview — chat nodes put a conversation inside a running flow.