Switcher and orchestration

What is Switcher

Switcher is a way of working with coding agents through a chat screen instead of a terminal. You see plans, tool runs, changed files, approval requests, and usage together inside the chat.

The engines that can open a Switcher chat are Claude Code, Codex, Antigravity (agy), OpenCode, and GitHub Copilot CLI. Claude Code, Codex, and Antigravity are marked 추천 (Recommended). The features each engine supports (rewind, goals, attachments, input while responding, and so on) differ, and for unsupported features the reason is shown.

Starting a new chat

In the left rail, open the ⋯ menu on a project row.
Choose a tool under 새 세션 (New session).
Supported tools offer separate CLI sessions and Switcher sessions. Choosing Switcher creates a new chat for this project using that tool's engine.

A new chat starts with the folder's defaults. If the folder has no values of its own, the global default is used. Set the defaults in "Defaults for new Switcher chats" in Connections and per-project settings.

Features inside a chat

Changing the model and reasoning effort

Choose the model and reasoning effort above the input box. You can search the model list or enter a model ID directly. The new values apply from the next message. They cannot be changed while a response or approval is being processed.

You can choose a reasoning effort only within the range confirmed to be supported by the selected model and the running tool. If support cannot be confirmed, the tool's default is sent and a notice is left.

Changing the running tool

You can switch the running tool of the same chat to a different tool. The session and its relationships are kept, and if needed, context is carried over using the original tool's compaction and a work summary. If the switch fails or there is not enough room to carry the context over, the existing session is left as is.

On the phone, in 대화 모델 바꾸기 (Change chat model), choose in the order provider → tool → model. The selected provider applies to this chat only, and the project settings do not change.

In a chat, press Ctrl+/ to open the command menu. You can run /help, /new, /stop, /model, /status, /search, /copy, /export, /retry, and /clear. For commands that cannot run right now, the reason is shown as well.

Chat info

Open 대화 정보 (Chat info) in the header to see the environment, context usage, branch, to-dos, changed files and diffs, subagents, and background tasks in one place.

Continuing a chat

When you reopen the app, the Switcher chat list and the work layout are restored. Click 재연결 (Reconnect) in the chat you want to continue to carry on with the same chat. Merely reading the list does not launch the CLI.

AI code review

Review changes before committing from Switcher's ⋯ more menu → AI 코드리뷰 (AI code review). Changes are sent over a connection only after you choose a connection with a saved API key and a model, and click 리뷰 실행 (Run review). Opening or refreshing the screen alone does not call the model.

Voice chat

Turn on 환경 설정 › 음성 대화 (Settings › Voice chat) and choose an OpenAI API connection, then use 음성 대화 (Voice chat) in the Switcher header to talk with the current session. It is off by default. Audio is sent directly to OpenAI with your OpenAI API key and billed to that key. Stopping work and approvals are carried out only after you confirm them on screen.

Orchestration

Orchestration lets one Switcher chat (the coordinator session) create other sessions (workers) and assign work to them. Workers can report results or ask the coordinator session questions.

Designating a coordinator session

Open the Switcher chat you want to act as coordinator.
Click 오케스트레이션 세션으로 지정 (Designate as orchestration session).
Choose a mode in 오케스트레이션 권한 선택 (Choose orchestration permissions).
- 사용자 승인 후 위임 (Delegate after user approval): You confirm delegations, such as creating or instructing workers, before they run.
- 전체 자율 위임 승인 (Approve fully autonomous delegation): Explicitly delegated input is delivered without further approval.

Choosing, approving, and revoking permissions can only be done in the user interface. The existing engine's approval rules and working folder restrictions remain in effect. The policy is stored encrypted on this PC.

Workers and tasks

The coordinator session creates workers in registered projects or resumes past sessions as workers. The model and reasoning effort can be set at creation.
A created worker appears as a single row under the project in the rail and opens as a background Switcher tab that does not take focus.
If a worker is busy, instructions and answers sent to it are held in a queue and delivered in order.
The coordinator session records user requests as 지휘 할 일 (Coordinator to-dos) and links them to worker tasks. Progress reported by a worker and completion confirmed by the coordinator after checking the result are shown separately.

Dashboard and relationship view

Open 오케스트레이션 대시보드 (Orchestration dashboard) from the coordinator session to see the coordinator, lead, and worker relationship view, task and delivery status, and the decision log. Delivery status shows only stages that were actually confirmed, such as 「승인 대기」 (Awaiting approval), 「전달 중」 (Delivering), 「입력 접수 · 완료 미확인」 (Input received · Completion unconfirmed), 「실행 여부 불명」 (Execution unknown), and 「완료」 (Completed). Requests whose execution status is unknown are not resent automatically.

You can also check and operate the orchestration dashboard and to-dos from the PWA and the Android app.

Lead permissions

The coordinator session can grant lead permissions to a direct worker. A lead manages its own sub-workers within the assigned projects and concurrency limit. Revoking the permission keeps the sub-workers' chats and runs.

Delegating to another PC

You can also create workers on another PC on the same account that you connected through 내 컴퓨터 (My computers) in the rail. The receiving PC must also set its orchestration permissions.

If the receiving PC is set to 위임마다 승인 (Approve each delegation), the work runs only after it is approved on that PC. If there is no response by the deadline, it is rejected.
If the receiving PC is set to 자율 위임 (Autonomous delegation), the work runs immediately.

The same request runs only once. Even if a response is lost, whether it arrived is reconciled using that PC's records. The other PC must be on the same version or later.

Cleanup rules

종료 (Stop) halts only processes launched by Switchboard and keeps chats, resume information, and relationships.
An idle worker's process is stopped after 15 minutes by default. A worker that reported its result and was stopped automatically is moved to the archive after 60 minutes by default.
Tasks waiting for approval, a question, or confirmation are excluded from automatic cleanup.
탭 닫기 (Close tab) does not end the session. A session restored from the archive can be resumed again.

In supervised mode (Delegate after user approval), this cleanup also requires user approval.

Language