ctx
ctx is a local toolchain for searching coding-agent histories, with additional Blame, graph and output-compaction capabilities. This review focuses on native Claude Code/Codex history retrieval. We downloaded the published macOS ARM64 binary 2.4.1 and matched its SHA-256 against GitHub release metadata, with source inspection at release commit 33ba4645b620fd89d138c6db1fabf33096a0ee16. On macOS 26.6.2, we used artificial native JSONL only, an independent data root, persisted manual indexing and disabled automatic source discovery.
Eighteen real CLI calls imported three sessions with five searchable events, searched across Claude/Codex, applied provider/workspace filters and read back exact event/session content including Chinese text. Repeat import left the selected hit singular and retained its IDs; input hashes confirmed that import did not rewrite the specimens. An appended sixth event was invisible with refresh off, then searchable after explicit incremental import. locate returned Core source and provider identities, rather than a physical original-file path.
Adding one malformed line left valid content searchable and returned completed_with_rejections with a rejection count of one, while exiting zero. Callers should inspect the structured outcome when partial rejection matters. A fake token-like marker survived raw readback, so retrieval is not automatic redaction. Native roots must be directories with matching session identities. Explicit imports still use finite workers in manual mode. We did not test personal logs, semantic models, provider-wide recall, Blame, graph, Sift, persistent daemon operation, hosted sharing, other OSes or README speed/token ratios.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-05
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 30
- Latest release
- v2.4.1 (2026-11-05)
- Open issues
- 3
- Recent issues with at least one comment
- 6/15
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #1178 2.4.1 import --all cannot upgrade a 2.3.0 index: retired route was not carried0 comments · 2026-11-06
- #1177 Windows: Devin import fails because a missing sessions.db-journal surfaces as SystemIo, not NotFound0 comments · 2026-11-05
- #1167 Replace paste with a compatible upstream tokenizer dependency0 comments · 2026-11-05
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You need to recover decisions and failed approaches from existing coding transcripts.
- You can verify source roots, refresh policy, exact readback and import diagnostics.
- You require verified semantic or code-attribution capabilities from this review.
- You expect retrieval to redact everything automatically or always return physical file locations.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!