command-center

KO | EN

gitlite — search

#machine-learning #sql #nextjs #electron #open-source #computer-vision #claude #database #terminal #chatgpt

(★ 9)

Local dashboard + CLI for browsing and searching your AI coding sessions - Claude Code, OpenCode, Kimi, Grok, and more, in one place

파일 탐색기

ZIP 다운로드

- AmpSessions.php
- AntigravitySessions.php
- ClaudeSessions.php
- CodexSessions.php
- CommandCodeSessions.php
- FlowExtractor.php
- GeminiSessions.php
- GrokBotSessions.php
- GrokSessions.php
- Helpers.php
- KimiSessions.php
- OpenCodeSessions.php
- Retention.php
- Router.php
- SearchIndex.php
- SessionRegistry.php
- T3CodeSessions.php
- Updater.php
- app.js
- apple-touch-icon.png
- favicon-32.png
- favicon.svg
- style.css
- .gitkeep
- shell.php
.gitignore
api.php
CHANGELOG.md
command-center
command-center-cli.md
index.php
LICENSE
manifest.json
README.md
reindex.php
stream.php

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

A local dashboard + CLI for browsing and searching your AI coding sessions - every conversation, across every tool, in one place.

If you bounce between AI coding CLIs, your conversation history ends up scattered across half a dozen dot-directories. Command Center indexes all of them into a single searchable timeline: skim what you worked on each day, deep-search full conversation content, replay any session, and copy a ready-to-run resume command.

**Your index stays on your machine.** Command Center reads local transcript files and builds its search index in a local SQLite database. For current Amp threads, it uses the installed `amp` CLI to list and download your own thread exports on demand. Command Center does not upload conversation data anywhere.

## Supported tools

| Tool | Reads from | Token usage |
|---|---|---|
| Amp | Local snapshots + `amp threads` | ✅ |
| Claude Code | `~/.claude` | ✅ |
| OpenCode | `$XDG_DATA_HOME/opencode` | ✅ |
| Kimi CLI | `~/.kimi` | ✅ |
| Command Code | `~/.commandcode` | estimated |
| T3 Code | `~/.t3` | estimated |
| Antigravity | `~/.gemini/antigravity-cli/brain` | - |
| Gemini CLI | `~/.gemini/tmp` | ✅ |
| Grok Build | `~/.grok` | ✅ |
| Grok Bot | `~/Library/Application Support/Grok Bot` | estimated |
| Codex | `~/.codex` (ChatGPT / VS Code Codex) | ✅ |

Tools you don't use are skipped automatically. Each location can be overridden with an env var (`AMP_HOME`, `CLAUDE_HOME`, `OPENCODE_HOME`, `KIMI_HOME`, `COMMANDCODE_HOME`, `T3CODE_HOME`, `ANTIGRAVITY_HOME`, `GEMINI_HOME`, `GROK_HOME`, `GROKBOT_HOME`, `CODEX_HOME`).

## Features

- **Session index** - every session from every tool in one reverse-chronological list, grouped by day, filterable by tool and project. Nested subagents expand under their parent where the tool records them.
- **Deep search** - SQLite FTS5 full-text search across conversation content, with snippets and highlighting. The index updates incrementally; only changed sessions are re-read. Status shows listed / indexed / skipped / stale coverage.
- **Session viewer** - replay any conversation: user messages, assistant responses, collapsible tool-call groups, and turn summaries. Large sessions paginate (1000 events per page) so the tab stays responsive.
- **HTML export** - save any conversation as one self-contained HTML file, no assets and no server needed. Defaults to the chat-only view with injected context folded away, and opens in the reader's preferred colour scheme.
- **Resume commands** - one click copies the exact CLI command to resume a session in its original tool and project directory (OpenCode, Kimi, Claude, Grok, and others; T3, Codex, and Grok Bot open the desktop app).
- **Activity heatmap + usage** - GitHub-style sessions-per-day graph with token tooltips; monthly usage page for input / output / cache across providers. Opening a session parks the dashboard DOM so back restores it without refetching.
- **Token tracking** - recorded usage where tools expose it (including Grok Build `turn_completed.usage`, with parent sessions summing nested subagent bills); estimated usage for Command Code, T3 Code, and Grok Bot.
- **Runtime tracking** - active time per session computed from transcript timestamps (Claude Code, OpenCode, Codex), with idle gaps over 5 minutes excluded so a chat left open all day reads honestly. Sessions with a 30-minute-plus uninterrupted stretch are flagged as the agent-went-off-and-worked signal, without printing the same figure twice or spending a column: one that ran straight through gets its duration tinted, one that was broken up gets a dotted underline, with the stretch itself named in the tooltip. Active hours roll up on the heatmap tooltips and the usage page.
- **Retention monitor** - optional per-provider TTL warnings when agent tools auto-delete old transcripts.
- **Row identity + live state** - one chip per row carries the model, tinted with its tool's colour (Grok Build and Codex include reasoning effort), backed by a source dot on the left rail; a session still running pings that dot. Grok Build adds duration/tools/LOC and context window when signals are present.
- **Index health** - listed / indexed / skipped / stale coverage in a dashboard popover next to reindex (not in the nav).
- **Self-update** - nav version chip checks GitHub once a day on dashboard load; Update applies a git pull or the release package. Same engine as `command-center update`.
- **`command-center` CLI** - search and inspect your history from the terminal, including `flow`: reconstruct how a project was built from its transcripts.

## Install

Command Center is a plain PHP app (PHP 8.1+ with the `sqlite3` extension - no database server, no build step). It needs a local web server that routes requests through `index.php`.

### Recommended: Cove

[Cove](https://cove.run) is a zero-config local dev environment for macOS (Caddy + FrankenPHP). With Cove installed:

```bash
cove add command-center --plain
cd "$(cove path command-center)"
rm index.php   # Cove's placeholder landing page
git clone https://github.com/austinginder/command-center.git .
```

Then open **https://command-center.localhost** - sessions appear immediately, and the search index builds on first deep search (or click the refresh button next to the project filter).

### CLI

Symlink the bundled script onto your `$PATH` (from the site directory):

```bash
ln -s "$(pwd)/command-center" ~/.local/bin/command-center
```

```bash
command-center "error handling"          # search everything
command-center "webhook" -p my-project   # scope to a project
command-center sessions                  # list sessions
command-center flow my-project           # how a project was built
command-center status                    # index health
```

Full CLI reference: [command-center-cli.md](command-center-cli.md).

### Updating

The dashboard nav shows the installed version and checks for updates once per day (cached server-side). When a newer release is available, click **Update** in the version panel - or use the CLI:

```bash
command-center version          # installed version
command-center update --check   # is a newer release available?
command-center update           # update in place
```

Both the UI and CLI compare the local `manifest.json` against the latest release manifest on GitHub (`main`). Git installs are updated with a fast-forward pull (they refuse if the working tree has local changes). Non-git installs download the release package (`command-center.zip` from the GitHub release) and copy it over the install, leaving `data/` untouched.

| Flag | Effect |
|---|---|
| `COMMAND_CENTER_UPDATE_CHECK=0` | Disable remote checks |
| `COMMAND_CENTER_UPDATE_SIMULATE=1.8.0` | Pretend remote latest is `1.8.0` (UI/CLI show Update; apply is a dry-run) |
| `COMMAND_CENTER_UPDATE_SIMULATE=1` | Pretend remote is local patch+1 (e.g. `1.7.0` → `1.7.1`) |
| `data/update-simulate` | Same values as a one-line file (handy for the Web UI; stays under gitignored `data/`) |

```bash
# CLI
COMMAND_CENTER_UPDATE_SIMULATE=1.8.0 command-center update --check

# Web UI (no Cove env plumbing needed)
echo 1.8.0 > data/update-simulate
# hard-refresh dashboard → UPDATE badge
# remove when done:
rm data/update-simulate
```

## API

Everything the UI does is available as JSON under `/api`:

```
GET  /api/sessions                     list sessions (?source=, ?project=)
GET  /api/sessions/projects            list projects
GET  /api/sessions/sources             available providers
GET  /api/sessions/search?q=           deep search (?source=, ?project=)
GET  /api/sessions/search/status       index health (listed / indexed / skipped / stale)
GET  /api/sessions/stats/daily         per-day counts + token totals + active seconds
GET  /api/sessions/stats/monthly       per-month token totals + active seconds by source
GET  /api/sessions/{id}                session meta (incl. nested subagents)
GET  /api/sessions/{id}/conversation   paginated events (?limit= up to 1000, ?offset=; omit offset for tail)
POST /api/sessions/search/reindex      rebuild the index
POST /api/sessions/tokens/backfill     backfill token usage for indexed sessions
POST /api/sessions/timings/backfill    backfill runtime stats for indexed sessions
GET  /api/retention                    retention report (?prefer= preferences)
GET  /stream?session={id}              SSE replay of a session
```

## Privacy

Your conversation history is sensitive. Command Center is designed to be run **locally only**:

- All transcript reads and the FTS index live on your machine (`data/` - gitignored).
- No analytics, no phone-home. (The UI shell loads Tailwind, marked.js, and fonts from CDNs. Update checks contact GitHub at most once per day when the dashboard loads, or when you run `command-center update`.)
- Don't host it on a public server unless you put authentication in front of it - the app itself has none.

## Adding a provider

Each tool is one self-contained class in `app/` implementing the provider contract documented in [`app/SessionRegistry.php`](app/SessionRegistry.php) - list sessions, extract searchable text, fingerprint for incremental indexing, stream a conversation, and (optionally) report token usage. Register it in `SessionRegistry::providers()` and `index.php`, and the UI, search, CLI, and heatmap pick it up automatically.

## License

[MIT](LICENSE)

command-center

파일 탐색기

# CDN으로 사용하기

Was this content helpful?

Recent Feedback

Download README