The Claude Code view

What it’s for

Escouade’s conversation shows the essentials of an agent’s work, but not everything Claude Code offers. In its own interface, you get all of it: / commands, shortcuts, dialogs, /model, Shift+Tab to change mode… It’s useful when you want to work the way you would in a terminal, while keeping the agent in Escouade’s list with its statuses, notifications, and cost.

Switching views

In an agent’s conversation header, the “Claude Code view” button (>_) launches Claude Code’s interface in a terminal that takes the place of the conversation. The button becomes “Escouade view” (◧): a click takes you back to the conversation. The session is the same in both directions: Escouade stops the process of one view and resumes the session in the other (--resume), so the agent forgets nothing. The choice is kept for each agent. The interface starts when you show the agent (the terminal then says “Starting Claude Code…”), including after Escouade restarts, and picks up its session.

Switching to the Claude Code view is refused in three cases, with a message; switching back to the Escouade view is refused in none of them:

• The agent is still working: switch views once its turn is over.
• Remote control is on: turn it off first. In Claude Code’s interface, its /remote-control command does it (see remote control).
• The agent works on a ticket: a ticket agent stays in Escouade’s view, which its board drives (see the Kanban). The button doesn’t exist for it, nor for an archived agent.

If the interface stops (you typed /exit, or the process was killed), the terminal shows “Claude Code stopped.” and a “Restart” button; if it doesn’t start, “Claude Code didn’t start:” followed by the error, with the same button. Archiving or deleting the agent also closes its terminal.

What Escouade keeps tracking

Claude Code’s interface is a terminal, but Escouade still knows what the agent does. It reads it in two ways: Claude Code’s hooks, which the interface calls on your machine (127.0.0.1, with a token of its own for each interface), and the session’s transcript, which the app rereads continuously. Your own hooks stay active.

Thanks to this, an agent in the Claude Code view keeps:

• its dot and its statuses: “Running”, “Question” when it’s waiting for a permission or an answer, “Done” at the end of a turn;
• its notifications: the blinking, the chime, and the system notification when it’s waiting for a permission or an answer, then when it finishes (see notifications);
• its conversation: what happens in the interface is also written to Escouade’s conversation, which you find again when you return to the “Escouade view”;
• search (Ctrl+K, see keeping track of your agents);
• the “Plan” banner (see plan progress);
• its statistics and its cost (see statistics). The interface doesn’t give the cost of each turn: Escouade estimates it from public prices.

When the agent is waiting for an answer, you give it in the terminal: the overview reminds you (“Waiting for your answer in Claude Code’s interface”) and its “Reply” button opens the agent.

Writing to an agent in this view

Escouade’s message field isn’t shown: you write in the terminal, as in Claude Code. To attach a file, paste it into the terminal.

A message sent to the agent from elsewhere, for example through the MCP server, is typed into its interface. It’s refused while the agent is waiting for an answer in its terminal (“The agent is waiting for an answer in its terminal: answer there first.”). An interruption requested from Escouade becomes the Esc key in the interface.

Opening new agents in this view

In Settings › Claude Code, group “New agents”, the “Open new agents in Claude Code’s interface” switch (off by default) makes each new agent start in this view. Each agent can then switch views from its header. Ticket agents always stay in Escouade’s view. See the Claude Code settings.

Folder trust

The first time Claude Code’s interface launches in a folder, it asks whether you trust it. Escouade never answers for you. Worktrees created in the project’s default worktrees folder (.claude/worktrees) inherit the answer given for the project. A “Worktrees folder” outside the project doesn’t inherit it: the interface asks the question the first time each worktree is launched (see worktrees).

On Windows with WSL

When Claude Code is installed in WSL, Escouade launches it through wsl.exe (see the Claude Code settings). Live tracking of the Claude Code view then requires WSL’s mirrored networking: without it, the interface’s hooks don’t reach the app. The settings point it out under the claude path (“WSL’s network is NAT…”). To switch to mirrored mode, add this to %UserProfile%\.wslconfig, then run wsl --shutdown:

[wsl2]
networkingMode=mirrored