Navigate through many CC instances and local worktrees.
Manage multiple sessions and repos.
All from one single tool.
Install it with a single command:
npx jacquesNo global install needed. First run auto-detects missing setup and walks you through it.
Available for macOS, Windows, and Linux.
Features • Who Is This For • Commands • Architecture • Roadmap • Development
npx jacques
That's it. First run detects missing setup and launches the interactive wizard automatically. After setup, you go straight to the dashboard.
Need to reconfigure later? Run npx jacques setup anytime.
Other ways to install
# Global install (faster startup after first run)
npm install -g @jacques-ai/cli
jacques
# pnpm
pnpm add -g @jacques-ai/cli
jacques
# bun
bunx jacques
bun add -g @jacques-ai/cli
jacquesnpx vs global install: npx runs directly without installing — great for trying it out. A global install (npm i -g) means jacques is always available and starts faster since it skips the download step.
Requirements: Node 20+, Python 3.8+, Claude Code.
No more running blind between multiple opened terminals, tabs, worktrees and projects.
Everything available from inside a single app — monitor, focus, tile.
One-click to spawn new Claude Code instances and create new worktrees per task.
Never lose track of uncommitted changes on the 107th worktree you've created.
Just starting with vibe coding — feeling overwhelmed with multiple terminal instances, having a hard time keeping good practices with your workflow. Jacques gives you one place to see everything.
Pre-AI era coders who fully embrace the shift — but feel the headache with these new dynamic, multi-context workflows and gitflows you have to apply now. Jacques keeps it organized.
Multiple screens, dozens of agents — working on different things across different repos. Jacques helps you keep track of all of it.
13-inch MacBook, single screen — a single CLI window will help you get the most out of limited space.
Jacques stays simple but powerful. Inside there are a few modules and some additional resources. During the setup process you decide what to install.
A terminal TUI that shows real-time context usage %, session status, and plan progress for every active Claude Code session. Keyboard-driven — focus sessions, tile terminal windows into a grid, spawn new sessions, and manage git worktrees without ever leaving the dashboard.
Full browser dashboard at localhost:4243. Browse session history, view extracted plans and subagent results, manage worktrees, launch sessions. Your entire Claude Code conversation archive — searchable.
[Opus] ctx:42% displayed right inside Claude Code. No window switching needed — context usage is always visible.
/jacques-handoff and /jacques-continue — structured session handoffs inspired by ops shift-handoff protocols (SRE/ITIL). Each handoff captures progress with file paths and function names, user decisions with reasoning, plan status, failed approaches and why, warnings and gotchas, and prioritized next steps — so the next session starts with full context instead of re-discovering everything from scratch.
Every session is auto-cataloged on exit — even if you Ctrl+C. Plans, subagent results, and session manifests are extracted and saved. Full-text search across all past conversations, filterable by project, date range, and technology.
Native OS notifications for events that matter — context thresholds (50%, 70%), plan creation, auto-compact, and handoff generation. Works across macOS (with click-to-focus), Linux, and Windows. The web GUI adds in-app toasts and a notification center with read/unread tracking. Opt-in via Settings with per-category toggles.
The setup wizard lets you choose what to enable. Install just the lightweight CLI, add the web GUI for history browsing, or include skills for session continuity.
The first release was built for a vibeathon organized by BridgeMind.
It's early, and it needs improvements. This is a preview of what Jacques will eventually become — your next coding assistant.
More features on the way.
| Command | Description |
|---|---|
jacques |
Start dashboard + embedded server |
jacques setup |
Interactive setup wizard (re-run anytime to reconfigure) |
jacques status |
Show current session status |
jacques list |
List active sessions as JSON |
jacques search <query> |
Search archived conversations |
jacques archive-stats |
Show archive statistics |
jacques update |
Check for and install the latest version |
jacques --version |
Show version |
jacques --help |
Show all commands |
Search options: -p/--project, --from/--to, -t/--tech, -l/--limit, --json
| Script | Description |
|---|---|
npm run start:server |
Server + web GUI only |
npm run dev:gui |
GUI dev server (hot reload) |
npm run build:all |
Rebuild all packages |
npm run stop:server |
Stop running server |
Claude Code (hooks)
│ IPC Socket (/tmp/jacques.sock)
▼
┌─────────────────────────────────┐
│ Jacques Server (Node.js/TS) │
│ WebSocket :4242 │ HTTP :4243 │
└─────────────────────────────────┘
│ │
▼ ▼
CLI TUI Web GUI
(terminal) (localhost:4243)
Claude Code hooks report lifecycle events (start, tool use, idle, context updates) over an IPC socket. The server aggregates state and broadcasts to connected clients. Running jacques starts the server, CLI, and web GUI in a single process.
| Item | Location |
|---|---|
| Jacques data | ~/.jacques/ |
| Hook config | ~/.claude/settings.json |
| Per-project catalog | {project}/.jacques/ |
Environment variables (all optional):
| Variable | Default | Purpose |
|---|---|---|
JACQUES_WS_PORT |
4242 |
WebSocket port |
JACQUES_HTTP_PORT |
4243 |
HTTP API port |
See docs/PLATFORM-SUPPORT.md for Windows paths and cross-platform details.
Sessions not appearing
Restart Claude Code to pick up the new hooks. Verify hooks are installed:
cat ~/.claude/settings.json | grep jacquesIf missing, re-run npx jacques setup.
Server won't start
A zombie process may be holding the port:
npm run stop:server # Kill zombie process
rm /tmp/jacques.sock # Remove stale socket (macOS/Linux)
lsof -i :4242 -i :4243 # Check port conflictsStatusLine not showing
Re-run npx jacques setup and make sure StatusLine is enabled in the options step. Restart Claude Code after setup.
CLI shows "Disconnected"
The server isn't running. Start it with jacques or npm run start:server.
For other issues, open a GitHub issue.
Does Jacques slow down Claude Code?
No. The hooks are lightweight Python scripts that send a single message over a Unix socket. Overhead is negligible.
Do I need to keep the CLI open?
No. The StatusLine integration works independently — context % shows inside Claude Code without any external window. The CLI and web GUI are optional views.
Does it work with multiple projects?
Yes. Jacques discovers all your Claude Code projects automatically and groups sessions by git repo. Switch between projects in the CLI or web GUI.
What happens when a session is killed with Ctrl+C?
Jacques detects the dead process within 30 seconds and extracts the session's plans, subagent results, and manifest to your project's .jacques/ directory. Nothing is lost.
Can I use this with Cursor?
Partial support. Jacques can monitor Cursor sessions but hook integration is still experimental.
git clone https://github.com/gregory-lime/jacques.git
cd jacques
npm run setupBuild order: core → server → cli → gui (each depends on the previous).
npm run dev:server # Server with tsc --watch
npm run dev:gui # GUI with Vite hot reload
npm run build:all # Full rebuildcd server && npm test # Server tests
cd core && npm test # Core tests
cd cli && npm test # CLI testsSee CLAUDE.md for the full development guide.
Built for developers who run Claude Code at scale.






