Up to ? runs execute in parallel (set CCC_MAX_CONCURRENT_RUNS).
Extra tasks queue. Two write-capable tasks in one folder never run at once unless you choose “Run anyway”.
Sessions
A session is one Claude conversation with a stable id. Opening a session starts no Claude
process and costs nothing — it only mints the id. The first request you send starts
Claude and binds the conversation to it; every later request continues that same
conversation instead of starting a new one.
Loading sessions…
Couldn't load sessions.
No open sessions yet — open one above.
Select a session on the left, or start a new one.
archived
—Session unavailableconnecting
Quality control
—
Waiting for Claude credits
Paused
Plan
—
from your voice
nothing runs until you press Run Plan
Plan Mode settings—
Read the Persian summary above, reply to it, and keep going until the plan is right. When
it is, Run Plan turns the whole conversation into one implementation prompt — and asks
you how to execute it.
Implementation prompt generated from this plan
Confirm what was heard
nothing has run yet
Claude’s understanding (Persian)
Request that will be sent if you confirm
Queued for this conversation
Technical activity — Claude execution / Control Center / Integrations
Context token usage is not available from Claude CLI.
Git & changed files
Before
—
After
—
Per-file changes, with diffs, are in Changed files above.
Diff
—
Review with Codex (prepare only — nothing is sent)
Remote Control (personal Claude subscription — cannot continue a claude -p session)
Starts an official Claude Code Remote Control session for the project folder above, using the
account claude is already signed into. No API key, token or password is used,
stored or shown. It is not a programmatic API and cannot submit prompts; the Session badge
reads “Session unavailable” for Remote Control.