Files
nntrivi2001 17d56d0e01 refactor!: rebrand CCAM to AgentHub
Clean break, no compatibility alias. Renames the product name, the CLI
binary (`ccam` -> `agenthub`), the env var prefix (`CCAM_` ->
`AGENTHUB_`), the Prometheus metric namespace (`ccam_*` ->
`agenthub_*`), the tmux session prefix (`ccam-lane-<id>` ->
`agenthub-lane-<id>`), the per-repo runtime profile directory
(`.ccam/profile` -> `.agenthub/profile`), the lanes state root
(`~/.claude/ccam-lanes` -> `~/.claude/agenthub-lanes`), the bundled
plugins (`plugins/ccam*` -> `plugins/agenthub*`) and their slash
commands (`/ccam-doctor` -> `/agenthub-doctor`, `/ccam:*` ->
`/agenthub:*`).

Because there is no alias, an existing install has to be updated by
hand: rename its `.ccam/profile` directory and any `CCAM_*` variables,
and reinstall the plugin under its new name.

Two other name families are deliberately left alone here, since they are
not just strings: the `Claude-Code-Monitor` repository/marketplace name,
and the `agent-dashboard` npm package plus its `~/.claude/agent-dashboard`
runtime directory, which holds the live database and needs a migration
rather than a rename.

Verified: server 1406/1406, client 459/459, `grep -i ccam` clean across
tracked files, `openapi.yaml` regenerated (95 paths, unchanged count).
2026-09-07 12:09:15 +07:00

1.4 KiB

description, argument-hint
description argument-hint
Search Agent Monitor sessions by cwd, model, or status and print the top matches. [query]

Search Claude Code sessions tracked by the Agent Monitor and print the top matches.

The query is $ARGUMENTS — any mix of a project / cwd substring, a model (opus/sonnet/haiku or a model-id fragment), and a status (active/working/completed/error). If empty, just show the most recent sessions.

Fetch the session list (each carries an inline cost field):

curl -s "http://localhost:4820/api/sessions?limit=200"

Then:

  1. Filter in-memory: keep sessions whose cwd contains the project term (case-insensitive), whose model contains the model term, and whose status equals the status term — apply only the terms present in $ARGUMENTS.
  2. Sort matches by cost descending if the query mentions cost/expensive, otherwise by started_at descending (most recent first).
  3. Print the top 10 as a numbered list, one line each: <rank>. <id short> — <status> — <model> — <cwd basename> — $<cost to 4dp> — <started_at>
  4. End with the match count and the summed cost of the shown matches.

Currency as USD to 4 decimal places. If nothing matches, say so and list the distinct cwds/models that DO exist (from the returned data) so the user can refine — do not invent results. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.