The ultimate monorepo for working with Claude Code — apps you run, utility tools, and shared libraries, all centered on Claude Code.
Each member keeps its own README.md and CLAUDE.md (plus a CHANGELOG.md once it is
released independently). This front page is the catalog; click into a folder for full docs.
Releases are tagged per component — see the release guide.
| App | What it does |
|---|---|
cross-repo-file-diff |
Survey many local repos from one board; diff and copy files across any two of them. Serverless, no build (Chromium only). |
multi-repo-plan-runner |
A command center over the Claude Code repos you work across: surface every plan and its lifecycle status, and run plans without leaving the tool. |
multi-repo-workspace |
Turn-based workspace over your Claude Code repos (internal name roundtable): a board of repos with live git/plan state, in-app Claude Code planning sessions, rounds of orders executed headlessly with live streams and per-run cost, and a review phase with diffs, commits, and carried follow-ups. Successor to multi-repo-plan-runner; both share the same lifecycle sidecar format. |
per-project-plugin-toggler |
Enable/disable Claude Code plugins per project from a browser UI or inside VSCode; browse and install from known marketplaces. |
usage-dashboard |
Interactive local web dashboard for token usage, cost, and rate limits: range/project scoping, plan ROI, trend deltas, activity/model/tool profiles, drill-down with shareable URLs, session economics, a live rate-limit trajectory with cap ETA, and Markdown/CSV export. Reads Claude Code transcripts; live rate limits come from the optional statusline-hook tool. |
claude-component-browser |
Local web app to search and read every Claude Code component — skill, agent, and hook — on your machine, from installed plugins and from loose (non-plugin) .claude skills/agents, grouped by source. |
| Tool | What it does |
|---|---|
statusline-hook |
Claude Code StatusLine hook (PowerShell/Bash/Python) printing a colour-coded one-liner; optionally exports JSONL for the usage-dashboard app. |
session-name-date-prefixer |
Prefix Claude Code session names with the date. |
file-sync |
Keep a named file in sync across two folders (newer wins): CLAUDE.md (raw copy) and settings.json (JSON merge, excluded keys preserved), via one generic engine. |
scheduled-session-digests |
Unattended scheduled Claude Code runs that digest your session transcripts into daily/weekly summaries and lessons. |
usage-report |
CLI summary of token usage and estimated cost across sessions — the terminal counterpart to usage-dashboard. |
statusline-hook,session-name-date-prefixer,claude-md-sync,settings-sync, and theusage-dashboardapp were originally oneclaude-automationsuite; seedocs/automation-suite.mdfor the combined overview.
| Library | What it does |
|---|---|
claude-usage |
Dependency-free library that reads Claude Code's ~/.claude/projects/**/*.jsonl transcripts into per-session token/cost data, plus the model pricing table. |
claude-plugins |
Dependency-free library that reads Claude Code's installed plugins and their skills/agents/hooks from local config into typed records. |
A library earns a place here only with a cohesive domain and ≥2 real consumers — not as a
utilities junk drawer. claude-usage qualifies (the transcript layout, consumed by the
usage-dashboard app and the usage-report CLI); so does claude-plugins (the installed-plugin
layout, consumed by the claude-component-browser and per-project-plugin-toggler apps).
The installable tools/ members (statusline-hook, session-name-date-prefixer, file-sync,
scheduled-session-digests) can be installed, uninstalled, and tracked from one place via
setup/command-center.ps1:
./setup/command-center.ps1 status # what's installed on this machine
./setup/command-center.ps1 install -Member statusline-hook
./setup/command-center.ps1 install -All # reads ~/.claude-command-center/config.json
./setup/command-center.ps1 uninstall -AllIt delegates to each tool's own setup script and records state in a manifest under
~/.claude-command-center/. See setup/README.md. Apps and usage-report
are run on demand, not installed, so they are not managed here.
Every environment variable this repo defines is prefixed C4_ (the repo's own namespace) so it
never collides with Claude Code's or the OS's variables:
| Variable | Used by | Purpose |
|---|---|---|
C4_CLAUDE_DIR |
usage-report, usage-dashboard, setup/ |
Override the Claude config dir (default ~/.claude); pathsep-separated, first entry wins. |
C4_CLAUDE_META_DIR |
scheduled-session-digests, setup/ |
Location of the claude-meta directory (default ~/claude-meta). |
C4_STATUSLINE_EXPORT |
statusline-hook |
Opt-in to the JSONL export when set to 1/true/yes. |
C4_STATUSLINE_LIVE_TIMEOUT |
usage-dashboard |
Seconds a session may be idle before dropping out of the live view (default 1800). |
C4_PLAN_PRICE_USD |
usage-dashboard |
Monthly Claude subscription price; lights up the dashboard's Plan Value (ROI) card when set. |
C4_ROUNDTABLE_REGISTRY |
multi-repo-workspace |
Registry file path (overridden by --registry, ahead of ./.roundtable.json). |
C4_ROUNDTABLE_HOME |
multi-repo-workspace |
App state dir — rounds, session transcripts, run output (default ~/.roundtable). |
OS-provided variables (USERPROFILE, LOCALAPPDATA, PATH, …) are not ours and keep their names.
apps/ full applications you run
tools/ single-purpose utilities & scripts
libs/ shared libraries
setup/ unified installer for the tools/ members + per-machine manifest
plugins/ packaged Claude Code skills/plugins (planned)
docs/ monorepo-wide docs
cheneeheng/agent-skills— the Claude Code skills/plugins marketplace (kept as a separate repo). It's the source of many skills you'd see in theclaude-component-browserapp here.
Apache-2.0 for the whole repository.
Agent decisions are logged in .agents_workspace/DECISION_LOG.md.
Historical per-member logs are consolidated in
.agents_workspace/archive/decision-log.md.