Tootega Cockpit for Claude CodeA rich GUI for Claude Code inside Visual Studio. The interface is only a presentation and control layer over the Claude Code CLI — all orchestration (agent loop, tools, subagents, context, cache, permissions, MCP, hooks, skills) lives in the CLI. Unofficial; not affiliated wit... |
Tootega Cockpit for Claude CodeClaude Code, with a full interface, inside Visual Studio. Everything the agent does already happens in the Claude Code CLI you have installed: the loop, the tools, the subagents, the context, the cache, the permissions, MCP, hooks and skills. What it does not have is a place to see any of it. That is what the Cockpit is — a presentation and control layer over the CLI, native to the IDE you already work in.
A conversation you can actually followStreaming token by token, with thinking blocks you can open when you want to know why, and a timeline that gives every tool call its own card — what it ran, on what, and what came back. Markdown is rendered with syntax highlighting and a line-number gutter, so a code answer reads like code. Long sessions stay navigable: a scroll rail marks each of your prompts, Control that arrives before the damageEvery tool call can be approved or refused with a preview of what it would do — allow once, allow always, or deny. Permission modes are a dropdown, including plan mode, where the plan is editable: correct it, send your notes back, and approve the version you actually want. Diffs are shown side by side, in the panel or in the Visual Studio diff viewer. Composed
questions from the agent come as real controls — tabs, multi-select, a free-text option.
Mention files with Know what it is spendingA live context window with the tokens left in it, cache life with a warning before it expires, cost per session, turns, compactions, and cache hit rates. No guessing how much room is left before compaction, and no surprise at the end of the month. Optionally, a local OpenTelemetry receiver aggregates what the CLI itself reports. It listens on localhost only, and conversation text is pinned out of telemetry. Written for people who writeAn inline spell-checker for English and Brazilian Portuguese, running on Hunspell in the host. It flags only what is wrong in both languages, so code identifiers and mixed-language prompts stay quiet — and it marks, never auto-corrects. Click an underlined word for suggestions grouped by language. Prefer to talk? Voice dictation with live partials, and an opt-in pass that cleans up the dictated text before it reaches the composer. One conversation, one windowEach conversation gets its own tool window, its own folder and its own CLI process, so two of them never share state. The folder is on the window's toolbar: it says where the conversation runs, and clicking it moves the conversation somewhere else. The Cockpit Hub is the other half — every saved context, the account, the plugins, MCP, skills and the consumption, in one place. It is one click from the title bar. Keys where keys belongAPI keys go into the Windows Credential Manager, not into a file next to the extension: a store you can inspect, audit and revoke through a normal Windows UI. Enrolment secrets for the credential vault are rendered as inline SVG QR codes, so they never touch disk. Getting started
Settings live in Tools ▸ Options ▸ Tootega Cockpit — engine, session defaults, interface, voice and the advanced switches. They mirror the VS Code extension, so nothing about the agent's behaviour changes when you move between editors. Shortcuts
Requirements
Nothing is spawned until you open a conversation. Installing the extension costs a package load and nothing else. PrivacyThe extension talks to the Claude Code CLI on your machine, and through it to Anthropic's endpoints. It has no telemetry of its own and phones home to nobody. The optional OTEL receiver listens on localhost and aggregates only what the CLI reports. Also for VS CodeThe same interface, from the same codebase: Tootega Cockpit for VS Code. LinksMIT licensed. Made by Tootega Pesquisa e Inovação. |