convez.ai
MCP Server
vishalguptax

claude-manager

vishalguptax/claude-manager

Ver no GitHub
BomPluginScore · de 0 a 100

Claude Manager — manage Claude Code sessions, MCP, skills, hooks, agents, accounts & usage from your VS Code sidebar. 100% local.

Instalação

$npx convez-ai vishalguptax/claude-manager

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
33
Forks
6
Acompanhando
0
Saúde
57%
Último commit
há 2 dias
Versão
2.21.1
Issues abertas
7
Contribuidores
2

README

A tradução para o português deste README ainda está na fila.

Install

VS Code • Cursor • Windsurf • Antigravity — open Extensions (Ctrl+Shift+X), search Claude Manager, click Install.

VSCodium • Theia • Gitpod — install from Open VSX.

Command line — code --install-extension vishalguptax.claude-manager

Open the panel

Three ways, pick whichever is closest:

WayHow
KeyboardCtrl+Alt+C on Windows/Linux — Cmd+Alt+C on macOS
Status barClick the Claude Manager chip at the bottom of the editor
Command paletteCtrl+Shift+P → Claude Manager: Open

That's it.

Why it exists

Claude Code is powerful, but the terminal isn't built for browsing. Finding a session you ran last week means scrollback hunting. Editing an MCP server means hand-patching JSON. Keeping track of every custom slash command, hook, and agent is its own job.

Claude Manager turns all of it into a sidebar you can click and search. Same Claude Code underneath — just one keystroke closer. Works whether you use the Claude Code CLI, the official VS Code extension, or both; sessions from either surface show up in the same list, and Resume routes back to the surface each session came from (configurable).

Whether you want to switch between Claude accounts in VS Code without a full logout/login, track Claude Code token usage and your 5-hour / 7-day subscription quota, manage MCP servers without editing JSON, browse and resume past Claude Code sessions by project and git branch, or organize your Claude skills, slash commands, hooks, and agents — Claude Manager keeps all of it one click away in your editor sidebar.

What's inside

Keyboard shortcuts

ShortcutAction
Ctrl+Alt+C / Cmd+Alt+COpen Claude Manager
Ctrl+Shift+P → Claude Manager: OpenCommand palette fallback
Ctrl+Shift+P → Claude Manager: Switch AccountNative quick-pick profile switcher
Ctrl+Shift+P → Claude Manager: ReloadFull re-parse + webview re-mount

Configuration

Open Settings (Ctrl+,) and search Claude Manager.

SettingDefaultWhat it controls
terminal.locationeditorOpen resumed sessions in the editor area or the bottom panel
terminal.editorPositionbesideWhich editor group terminals land in
sessions.defaultFilterrecentDefault date filter (recent / week / month / all)
sessions.defaultProjectcurrentDefault project scope (current workspace or all projects)
sessions.restoreWindowMinutes30Time window used to group terminals for Restore Workspace
sessions.resumeInautoWhere Resume / New / Continue opens Claude: auto (match the session's origin), terminal, extension (Claude Code chat tab), or ask (prompt each time)
marketplaceSkillsUrlunsetOverride URL for the in-panel Skills marketplace link
marketplaceMcpUrlunsetOverride URL for the in-panel MCP marketplace link

Full reference in docs/DEVELOPMENT.md.

FAQ

Does it send anything to the network? Local-first by default — zero telemetry, zero accounts, no background traffic. The extension reads from ~/.claude/ and renders in a VS Code webview. There is one opt-in exception: the Account tab's Quota card, which you must click to fetch. When you do, the extension makes a single GET https://api.anthropic.com/api/oauth/usage request with your own OAuth token (taken from ~/.claude/.credentials.json) to retrieve your subscription utilization. The token never leaves the extension host and nothing else is sent. Don't want it? Don't click Refresh — no network call happens.

How does the View button know which terminal hosts which session? Two passive signals, no instrumentation of Claude itself. (1) A SessionStart hook (auto-installed in your global ~/.claude/settings.json, removable) records each CLI boot's {sessionId, ppid} into ~/.claude/.claude-manager/active-sessions.json. The extension matches vscode.Terminal.processId against the recorded parent PID. (2) For VS Code terminals with shell integration, claude --resume <id> typed at any prompt is caught directly from the shell-execution event. cmd.exe (no shell integration) is covered by the hook path. Stale entries auto-prune after 1h or a dead PID.

Where are saved account profiles stored? ~/.claude/manager-accounts/<slug>/ — each slot holds a copy of ~/.claude.json and ~/.claude/.credentials.json plus a small profile.json with the label. These files include OAuth tokens (same plaintext format Claude CLI uses), so treat the folder as sensitive. Remove a profile and its token copy is deleted immediately.

Does it work with Cursor / Windsurf / Antigravity / VSCodium? Yes. It's a standard VS Code extension — install from the Marketplace (VS Code, Cursor, Windsurf, Antigravity) or Open VSX (VSCodium, Theia, Gitpod).

Do I need Claude Code installed? Yes — install Claude Code first. Either the CLI, the official VS Code extension, or both works. Claude Manager reads from the shared ~/.claude/ directory, so sessions from either surface show up together.

Does it modify my Claude config? Only when you explicitly act (enable/disable an MCP server, edit a permission, restore from a backup, rename or delete a session) — plus one bootstrap write on first activation: the SessionStart hook that powers the View button is added to ~/.claude/settings.json. Remove it from the Hooks tab if you'd rather not have it.

Where does my data live? In ~/.claude/ — same as Claude Code itself. The extension never copies, uploads, or duplicates your sessions.

Compatibility

Works on every VS Code-based editor: VS Code • Cursor • Windsurf • Antigravity • VSCodium • Theia • Codespaces • Gitpod

Requires VS Code 1.90+ and Claude Code installed. (On editors older than ~18 months, stay on the 1.10.x line.)

Contributing

Bug reports and PRs are welcome. See docs/DEVELOPMENT.md for local setup, build, and architecture. Browse open issues, open a new one, or check the changelog.

Architecture (v2): the webview is built with Preact + @preact/signals, feature-sliced under src/features/*/webview/, bundled by esbuild as a tiny shell that lazy-loads one code-split chunk per feature tab. Every message between the extension host and the webview flows through a single shared protocol validated at runtime with valibot, so malformed frames are rejected rather than acted on. The webview runs under a strict CSP (default-src 'none', nonce-only scripts) and makes no network calls. Lint + format is Biome; 1,381 unit tests gate every change. Upgrading from v1? See the v1→v2 migration guide — there's nothing you need to do.

Support

If Claude Manager saves you time, consider sponsoring the project. Sponsorship keeps development active and the extension free for everyone.

Disclaimer

Claude Manager is an independent, community-built extension. It is not affiliated with, endorsed by, or sponsored by Anthropic. Claude and Claude Code are trademarks of Anthropic, PBC — used here only to describe the files this extension reads on your machine.

Ver o original no GitHub

Bom para

Relacionados