Claude

Claude threads run the claude CLI you have installed and signed in. Cone streams the CLI’s JSON output into the transcript: reasoning, tool calls, file edits, shell commands, and token usage render live as the turn progresses.

Local turns

Local Claude turns run one CLI process per turn and resume the session id between turns, so conversation context carries across turns and app relaunches. The one-shot CLI path has no channel for answering permission prompts mid-turn, so local build turns run with permissions skipped and plan mode runs read-only. Remote threads get the full interactive permission flow, see Remote sessions over SSH.

Models and fast mode

The composer’s model picker carries the current Claude catalog. Fast mode, where the chosen model supports it, trades cost for output speed and is passed through to the CLI per turn.

Agent profiles

A profile is a named agent configuration: its own config directory, and optionally its own CLI binary. Use profiles to separate accounts, orgs, or experimental CLI builds. Each profile belongs to one provider. Claude profiles point CLAUDE_CONFIG_DIR at the directory, Codex profiles point CODEX_HOME. Assign a profile per thread from the composer’s status row, which offers the profiles matching the thread’s provider.

Profiles apply to local threads only. Switching a thread’s profile clears its resume id, because session state lives inside the profile’s config directory and the old id belongs to the previous one.