ARCH chat

Chat with ARCH

Loading your messages…

Talk to ARCH

Paste, drop, or choose files · 32 files · 100 MB each

Computer

Speak new repliesVoice

Voice is not configured or is still connecting.

Stop → review → send · AI voice

⌘ / Ctrl + Enter to sendRestoring draft…0 bytes · up to 128k tokensChat settings: Loading saved settings…

Your work

Connections · 0 / 0 computers

ARCH

ARCHConnecting

UpdatesReady

COMPUTERSChecking fleet

OBSERVED ACTIVE TASKSChecking work

Your work

Waiting for fresh observations

Checking your registered computers…

0–0 of 0

Computers & observation details

Live status uses native observations, not a generated name or an assistant’s completion claim.

Find a task

Conversations

Pick up where you left off.

Find a conversation

More filters

Include assistant subtasks Include archived conversations

No conversations found. Try another search or connect a computer.

0–0

Task settings & tools

Task settings · Codex · gpt-6.1-solProject edits allowed · Loading your settings…

Loading saved settings…

Changes save automatically for this chat. Account defaults are separate; already-submitted work keeps its original settings.

CONDUCTOR BRAIN · SERVER-SIDEGPT-6.1 Sol · medium · Ultra Fast

Loading available brain settings…

Brain request settings

Brain modelEnabled API models. Provider access is checked when a request runs.Brain reasoningThis brain uses the OpenAI API. Ultra belongs to the Codex runtime, not this API setting.Service tierOnly server-enabled tiers are offered. The actual tier is recorded.

CODING-AGENT EXECUTION · LIVE DESKTOPCodex · GPT-6.1 Sol · ultra

checking profiles

The selected live Desktop task manages its native tools and permissions. ARCH records the exact turn input, observable output, and application receipts; this is not CLI delivery. Provider-managed instructions are not exposed.

DestinationProject and context boundary

ProjectAuto lets Conductor ground the owner from current records.Conversation contextAuto finds relevant history. Selecting history does not itself create, fork, or resume a native task.

Execution laneExact provider, machine, model, and reasoning

Coding agentCodex continues Codex Desktop tasks; Claude Code continues Claude Code sessions. Switching agent unpins the other agent’s task and uses context in a new task. Claude Code · ultracode turns on Claude’s multi-agent workflows: a task may run many agents (up to 16 at once and 1,000 per run in Claude Code 2.1.296), take much longer and cost many times a standard run; ARCH sets no spending cap and shows Claude’s reported cost after each run. In a task that may change files the agents can edit files and run commands without asking; in a read-only run they can only read. It stays on for work that may change files while chosen here. Questions, control and conversation requests, and work asked to run read-only, run read-only and without it unless the message asks for ultracode; then they run read-only with it, also in a Claude session ARCH resumes. Asking in a message to turn it off applies to that request only. A Claude session that already has ultracode on keeps it for work sent there; a read-only request resumes it read-only without ultracode, which turns it off. ARCH sends nothing read-only to a session open in Claude.ComputerOnly a matching, machine-reported profile can execute.ModelUnavailable saved choices remain visible and are never substituted.Execution reasoningThis computer has not reported a compatible profile yet.DeliveryAutomatic Desktop delivery finds the relevant task or starts a separate task for unrelated work. An exact task below pins delivery to that task. ARCH never substitutes CLI for Desktop.

No fresh Desktop task connection is available yet. Open Codex Desktop on the intended Mac to finish connecting. Archived conversations remain available as context.

Desktop worker modePlan enables native questions and planning. This is separate from permissions. Code returns to the default working mode.

Behavior boundariesBusy work, writes, and fallback

If session is busyAsk, queue behind the current work, or start a separate session.Write policyDesktop keeps its own permissions. With normal policy you can request inspection without edits; ARCH cannot enforce a read-only sandbox in Desktop.FallbackARCH never silently swaps an unavailable execution profile.

Computer activity and available tools

Connecting to account activity…

Codex Desktop and Claude Code capabilities by computer — implemented is not the same as tested

Work across your computers · 0 active · Expand for progress, history, and evidence