COMMAND CENTER SESSION INDEX
~/.claude  ~/.kimi  ~/.grok  ~/.commandcode  ~/.t3  >>  one index

grep for your AI
coding sessions.

Every conversation you have with an AI coding CLI lands in a dot directory somewhere. Command Center indexes all of them into a single searchable timeline: skim what you worked on each day, deep search full transcripts, replay any session, and copy a ready to run resume command.

7 providers SQLite FTS5 plain PHP, no build step 0 telemetry MIT
$ cove add command-center --plain
view source →
command-center.localhost 1524 indexed · 77.3 MB
Search sessions · full conversation content Deep search
All 2418 Claude Code 2056 Command Code 86 T3 Code 6 OpenCode 107 Kimi 18 Antigravity 102 Grok Code 43
Mon Wed Fri
2,417 sessions in the last year · hover a day for tokens Less More
TODAY 4
claude How much is commandcenter.run and commandcenter.sh? 2.9 MB 11:31 AM
opencode Add SSE replay for the session viewer 1.8 MB 10:39 AM
kimi /quit 6.6 MB 5:27 AM
grok Why is the FTS index 77 MB and can we vacuum it 1.1 MB 1:11 AM
// 01 · supported tools

Seven CLIs. Zero config.

Tools you don't use are skipped automatically. Every location can be overridden with an env var.

TOOLREADS FROMTOKEN USAGE
Claude Code~/.claude
OpenCode$XDG_DATA_HOME/opencode
Kimi CLI~/.kimi
Command Code~/.commandcode·
T3 Code~/.t3·
Antigravity~/.gemini/antigravity-cli/brain·
Grok CLI~/.grok·

CLAUDE_HOME · OPENCODE_HOME · KIMI_HOME · COMMANDCODE_HOME · T3CODE_HOME · ANTIGRAVITY_HOME · GROK_HOME

// 02 · features

Everything, in one timeline.

[0x01]
Session index

Every session from every tool in one reverse chronological list, grouped by day, filterable by tool and project.

[0x02]
Deep search

SQLite FTS5 full text search across conversation content, with snippets and highlighting. The index updates incrementally; only changed sessions are re-read.

[0x03]
Session viewer

Replay any conversation: user messages, assistant responses, collapsible tool call groups, and turn summaries.

[0x04]
Resume commands

One click copies the exact CLI command to resume a session in its original tool and project directory.

[0x05]
Heatmap + tokens

A GitHub style contribution graph of sessions per day, with per day token usage on hover. Input, output, and cache totals per session.

[0x06]
command-center CLI

Search and inspect your history from the terminal, including flow: reconstruct how a project was built from its transcripts.

// 03 · install

PHP 8.1+, SQLite, done.

No database server, no build step. The fastest path is Cove, a zero config local dev environment for macOS. Any server that routes through index.php works too.

dashboard
$ cove add command-center --plain
$ cd "$(cove path command-center)"
$ rm index.php   # Cove's placeholder
$ git clone https://github.com/austinginder/\
    command-center.git .
then open command-center.localhost · sessions appear immediately
cli
$ ln -s "$(pwd)/command-center" \
    ~/.local/bin/command-center

$ command-center "error handling"
$ command-center "webhook" -p my-project
$ command-center flow my-project
$ command-center status
// 04 · api

The UI is just a client.

Everything the dashboard does is available as JSON under /api. Script it, pipe it, build on it.

GET/api/sessions · list sessions (?source=, ?project=)
GET/api/sessions/search?q= · deep search
GET/api/sessions/stats/daily · per day counts + token totals
GET/api/sessions/{id}/conversation · full parsed conversation
POST/api/sessions/search/reindex · rebuild the index
POST/api/sessions/tokens/backfill · backfill token usage
GET/stream?session={id} · SSE replay of a session
// 05 · privacy

Everything stays on your machine.

Command Center only reads local transcript files and builds its search index in a local SQLite database. Nothing is uploaded anywhere.

No analytics, no phone home, no external requests from the backend. The transcript data and FTS index live in data/, which is gitignored.

Your conversation history is sensitive. Run it locally only; the app ships with no auth, so don't put it on a public server without adding some.