quasar

name	quasar
description	Inspect and recover local Codex, Claude, and Hermes agent sessions with the Quasar CLI. Use when an agent needs to find session IDs for a project, resolve an exact rollout or transcript source file, read normalized session JSONL, search prior messages or tool activity, export a time window, or materialize a DB-only Hermes session.
metadata	{"version":"0.2.0"}

Quasar

Use quasar as the source of truth for local agent-session discovery. Keep data on stdout, diagnostics on stderr, and check the exit code before trusting an artifact.

Start

1. Run quasar doctor when provider storage or SQLite availability is uncertain.
2. Run quasar sessions --project-path "$PWD" --json to identify candidate sessions for the current project.
3. Narrow ambiguous IDs with --harness codex, --harness claude, or --harness hermes.

Resolve an exact source file

Run:

quasar session <id> --harness <provider> --source

Treat the single absolute path on stdout as the original provider file. If Quasar reports multiple candidates, add --project-path or a narrower --harness filter; never pick the first path heuristically.

Hermes sessions may exist only in SQLite. When Quasar reports a DB-only record, materialize generated normalized JSONL explicitly:

quasar session <id> --harness hermes --source --output /absolute/path/session.jsonl

Do not describe that generated file as the original Hermes payload.

Read or search a session

Emit normalized events or a readable conversation transcript for one session:

quasar session <id> --harness <provider>
quasar session <id> --harness <provider> --transcript
quasar session <id> --harness <provider> --transcript --with-tools --with-reasoning

Transcript mode excludes tools and reasoning unless explicitly requested.

Search across providers or one session:

quasar search "<query>" --since 7d
quasar search "<query>" --session-id <id> --harness <provider>

Export a reusable JSONL artifact:

quasar export <id> --harness <provider> --output /absolute/path/session.jsonl

Use --max-tool-result 0 only when complete tool payloads are required; the default truncation keeps agent context bounded.

Recover from misses

• Drop --project-path for DB-backed Hermes sessions whose project metadata is missing or stale.
• Retry with the filename-derived alias when a copied ID does not match the canonical metadata ID.
• Use --raw only for file-backed provider contents. Use normalized mode for DB-only Hermes records.
• Run the failing command with --help; every Quasar error includes What, Why, Fix, and Remediation fields.