AI coding assistant with real-time agent monitoring — VS Code extension and terminal dashboard.
AI coding agents are powerful but opaque — tokens burn silently, context fills up without warning, and everything is lost when a session ends. Sidekick gives you visibility into what your agent is doing, AI features that eliminate mechanical coding work, and session intelligence that preserves context across sessions. Works with Claude Max, Claude API, OpenCode, or Codex CLI.
Inline completions, code transforms, commit messages, session monitoring, and more — all inside VS Code.
Install from the VS Code Marketplace or Open VSX. See the full feature list in the docs.
Full-screen TUI for monitoring agent sessions — standalone, no VS Code required.
Note: The npm package is
sidekick-agent-hub, but the binary is calledsidekick.
npm install -g sidekick-agent-hub # requires Node.js 20+
sidekick dashboard
Browse sessions, tasks, decisions, knowledge notes, charts, and live event streams. Auto-detects your project and session provider. See the CLI Dashboard docs for keybindings and full usage.
Eight panels: Sessions, Tasks, Kanban, Notes, Decisions, Plans, Events, and Charts. The Events panel streams live session activity with colored type badges. The Charts panel shows tool frequency bars, event distribution, a 60-minute activity heatmap, and pattern analysis. Press / to filter with substring, fuzzy, regex, or date modes.
Standalone commands jump directly to a specific panel or run one-shot queries:
sidekick tasks # open tasks panel
sidekick search "migration" # cross-session search
sidekick stats # session statistics
sidekick quota # quota / rate-limit check
sidekick status # API status check (Claude + OpenAI)
sidekick peak # Claude peak-hours check (faster session-limit drain)
sidekick dump --format markdown > session-report.md
sidekick report # HTML report → browserAlso available: sidekick decisions, sidekick notes, sidekick handoff, sidekick context, sidekick quota, sidekick status, sidekick peak, sidekick account.
On first run, Sidekick auto-registers your active system Claude Code and Codex credentials as a "Default" account — no setup required. Use the flags below only when you want to add a second account or switch between them.
Manage multiple accounts for Claude Code and Codex — save, switch, and remove without manual login/logout cycles:
sidekick account # list saved accounts
sidekick account --add --label Work # save the current Claude Code account
sidekick account --switch # switch to next account
sidekick account --switch-to personal@gmail.com # switch to a specific account
sidekick account --remove old@example.com # remove a saved account
# Codex profiles
sidekick account --provider codex # list Codex accounts
sidekick account --provider codex --add --label Dev # add a Codex profile (opens login)
sidekick account --provider codex --switch-to Dev # switch by label, email, or IDIn VS Code, account actions are available from the status bar menu and the Command Palette — for both Claude Code and Codex providers. See the Claude Max and Codex provider docs for setup guides.
| Provider | Inference | Session Monitoring | Cost |
|---|---|---|---|
| Claude Max | Yes | Yes | Included in subscription |
| Claude API | Yes | — | Per-token billing |
| OpenCode | Yes | Yes | Depends on provider |
| Codex CLI | Yes | Yes | OpenAI API billing |
OpenCode note: DB-backed OpenCode session monitoring reads
opencode.dband currently expects an executablesqlite3runtime in the host environment.
AI coding agents are the most transformative tools I've used in my career. They can scaffold entire features, debug problems across files, and handle the mechanical parts of software engineering that used to eat hours of every day.
But they're also opaque. Tokens burn in the background with no visibility. Context fills up silently until your agent starts forgetting things. And when a session ends, everything it learned — your architecture, your conventions, the decisions you made together — is just gone. The next session starts from zero.
That bothers me. I want to see what my agent is doing. I want to review every tool call, understand where my tokens went, and carry context forward instead of losing it. Sidekick exists because I think the people using these agents deserve visibility into how they work — not just the output, but the process.
Full documentation is available at the docs site, including:
- Getting Started
- Provider Setup
- CLI Dashboard
- Feature Guide
- Configuration Reference
- Architecture
- Why Am I Building This?
Contributions are welcome! See CONTRIBUTING.md for setup instructions and guidelines.
sidekick-shared — the shared data access library, published as a standalone npm package. Types, parsers, session providers, event aggregation, model pricing, Zod schemas, and more — for building your own tools on top of Sidekick session data without depending on the VS Code extension or CLI. Install with npm install sidekick-shared.
Sidekick Docker — a sibling project that brings the same real-time dashboard experience to Docker management. Monitor containers, Compose projects, images, volumes, and networks from a keyboard-driven TUI or VS Code panel. Available as a VS Code extension, Open VSX extension, and CLI.
If Sidekick is useful to you, a star on GitHub helps others find it.
Found a bug or have a feature idea? Open an issue — all feedback is welcome.
MIT