[{"data":1,"prerenderedAt":30},["ShallowReactive",2],{"doc:en:claude-code-view":3},{"title":4,"lede":5,"html":6,"headings":7},"The Claude Code view","The Claude Code view runs an agent in Claude Code’s own interface, in a terminal, and brings it back to Escouade’s conversation without losing the session. This page explains how to switch views, what Escouade keeps tracking, and what changes.","\u003Ch2 id=\"what-it-s-for\">What it’s for\u003C\u002Fh2>\n\u003Cp>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: \u003Ccode class=\"key\">\u002F\u003C\u002Fcode> commands, shortcuts, dialogs, \u003Ccode class=\"key\">\u002Fmodel\u003C\u002Fcode>, \u003Ccode class=\"key\">Shift+Tab\u003C\u002Fcode> 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.\u003C\u002Fp>\n\u003Ch2 id=\"switching-views\">Switching views\u003C\u002Fh2>\n\u003Cp>In an agent’s conversation header, the “Claude Code view” button (\u003Ccode class=\"key\">>_\u003C\u002Fcode>) launches Claude Code’s interface in a terminal that takes the place of the conversation. The button becomes “Escouade view” (\u003Ccode class=\"key\">◧\u003C\u002Fcode>): 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 (\u003Ccode class=\"key\">--resume\u003C\u002Fcode>), 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.\u003C\u002Fp>\n\u003Cp>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:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>The agent is still working\u003C\u002Fstrong>: switch views once its turn is over.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Remote control is on\u003C\u002Fstrong>: turn it off first. In Claude Code’s interface, its \u003Ccode class=\"key\">\u002Fremote-control\u003C\u002Fcode> command does it (see \u003Ca href=\"\u002Fen\u002Fdocs\u002Fremote-control\u002F\">remote control\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The agent works on a ticket\u003C\u002Fstrong>: a ticket agent stays in Escouade’s view, which its board drives (see \u003Ca href=\"\u002Fen\u002Fdocs\u002Fboard\u002F\">the Kanban\u003C\u002Fa>). The button doesn’t exist for it, nor for an archived agent.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If the interface stops (you typed \u003Ccode class=\"key\">\u002Fexit\u003C\u002Fcode>, 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.\u003C\u002Fp>\n\u003Ch2 id=\"what-escouade-keeps-tracking\">What Escouade keeps tracking\u003C\u002Fh2>\n\u003Cp>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 (\u003Ccode class=\"key\">127.0.0.1\u003C\u002Fcode>, with a token of its own for each interface), and the session’s transcript, which the app rereads continuously. Your own hooks stay active.\u003C\u002Fp>\n\u003Cp>Thanks to this, an agent in the Claude Code view keeps:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>its dot and its statuses\u003C\u002Fstrong>: “Running”, “Question” when it’s waiting for a permission or an answer, “Done” at the end of a turn;\u003C\u002Fli>\n\u003Cli>\u003Cstrong>its notifications\u003C\u002Fstrong>: the blinking, the chime, and the system notification when it’s waiting for a permission or an answer, then when it finishes (see \u003Ca href=\"\u002Fen\u002Fdocs\u002Fnotifications\u002F\">notifications\u003C\u002Fa>);\u003C\u002Fli>\n\u003Cli>\u003Cstrong>its conversation\u003C\u002Fstrong>: what happens in the interface is also written to Escouade’s conversation, which you find again when you return to the “Escouade view”;\u003C\u002Fli>\n\u003Cli>\u003Cstrong>search\u003C\u002Fstrong> (\u003Ccode class=\"key\">Ctrl+K\u003C\u002Fcode>, see \u003Ca href=\"\u002Fen\u002Fdocs\u002Foverview\u002F#searching-conversations\">keeping track of your agents\u003C\u002Fa>);\u003C\u002Fli>\n\u003Cli>\u003Cstrong>the “Plan” banner\u003C\u002Fstrong> (see \u003Ca href=\"\u002Fen\u002Fdocs\u002Fplan\u002F\">plan progress\u003C\u002Fa>);\u003C\u002Fli>\n\u003Cli>\u003Cstrong>its statistics and its cost\u003C\u002Fstrong> (see \u003Ca href=\"\u002Fen\u002Fdocs\u002Fstats\u002F\">statistics\u003C\u002Fa>). The interface doesn’t give the cost of each turn: Escouade estimates it from public prices.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When the agent is waiting for an answer, you give it in the terminal: the \u003Ca href=\"\u002Fen\u002Fdocs\u002Foverview\u002F\">overview\u003C\u002Fa> reminds you (“Waiting for your answer in Claude Code’s interface”) and its “Reply” button opens the agent.\u003C\u002Fp>\n\u003Ch2 id=\"writing-to-an-agent-in-this-view\">Writing to an agent in this view\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>A message sent to the agent from elsewhere, for example through the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fmcp\u002F\">MCP server\u003C\u002Fa>, 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 \u003Ccode class=\"key\">Esc\u003C\u002Fcode> key in the interface.\u003C\u002Fp>\n\u003Ch2 id=\"opening-new-agents-in-this-view\">Opening new agents in this view\u003C\u002Fh2>\n\u003Cp>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 \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-claude-code\u002F\">the Claude Code settings\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"folder-trust\">Folder trust\u003C\u002Fh2>\n\u003Cp>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 (\u003Ccode class=\"key\">.claude\u002Fworktrees\u003C\u002Fcode>) 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 \u003Ca href=\"\u002Fen\u002Fdocs\u002Fworktrees\u002F\">worktrees\u003C\u002Fa>).\u003C\u002Fp>\n\u003Ch2 id=\"on-windows-with-wsl\">On Windows with WSL\u003C\u002Fh2>\n\u003Cp>When Claude Code is installed in WSL, Escouade launches it through \u003Ccode class=\"key\">wsl.exe\u003C\u002Fcode> (see \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-claude-code\u002F\">the Claude Code settings\u003C\u002Fa>). 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 \u003Ccode class=\"key\">claude\u003C\u002Fcode> path (“WSL’s network is NAT…”). To switch to mirrored mode, add this to \u003Ccode>%UserProfile%\\.wslconfig\u003C\u002Fcode>, then run \u003Ccode>wsl --shutdown\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-ini\">[wsl2]\nnetworkingMode=mirrored\n\u003C\u002Fcode>\u003C\u002Fpre>\n",[8,12,15,18,21,24,27],{"id":9,"text":10,"depth":11},"what-it-s-for","What it’s for",2,{"id":13,"text":14,"depth":11},"switching-views","Switching views",{"id":16,"text":17,"depth":11},"what-escouade-keeps-tracking","What Escouade keeps tracking",{"id":19,"text":20,"depth":11},"writing-to-an-agent-in-this-view","Writing to an agent in this view",{"id":22,"text":23,"depth":11},"opening-new-agents-in-this-view","Opening new agents in this view",{"id":25,"text":26,"depth":11},"folder-trust","Folder trust",{"id":28,"text":29,"depth":11},"on-windows-with-wsl","On Windows with WSL",1791926756216]