ctx CLI

A CLI for instant search across coding-agent session history on your machine, like git blame for sessions

  • 1,181 ★ on the repository
  • Last commit
  • Apache-2.0
CLI

Extended access

Why this level

  • Reads local coding-agent session history
All reasons and checks

ctxrs/ctx

Install

Manual install

curl -fsSL https://ctx.rs/install | sh

Package-manager installs and a source build are also available.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Reads local coding-agent session history

This is third-party code. Review the repository files before installing.

What it does

ctx searches the history already on your machine: coding-agent sessions, the flow of work, what was discussed and done and when. The tool is written in Rust and runs fast without loading history into a separate database. It helps recall the context of past work: find an event, open the session, get JSON output. It ships skills and plugins for agents, so the agent itself can search the history too. It installs with a single script, with package-manager and source-build options as well.

Who it is for. For developers who work with coding agents a lot and want to find past context quickly.

Good fit when

  • You need to recall what a past agent session did
  • You need to find a specific event or decision in the history
  • You want JSON output of the history for further processing

Not a fit when

  • You do not use coding agents whose history the tool reads
  • You need a full knowledge manager rather than session search

Example request

Find in the session history where we changed the build config and open that session

Limitations

The tool searches local session history, so it is only as useful as that history. The main docs and concepts live on the project site. Installation is via a script, package managers or a source build.

How to disable. Remove the ctx binary and uninstall any installed skills or plugins from the agent directories.

FAQ

Do I need a database?

No. ctx searches the on-disk history directly, without a separate relational database.

Can the agent search on its own?

Yes, it ships skills and plugins so the agent can call the history search.

Discussion

No questions or reviews yet.

CLI tools

CLI and TUI that search the local session history of Claude Code, Codex, Cursor, Gemini CLI and other agents, with a --robot mode for the agents themselves

CLIExtended access1.2KRepository stars

A CLI that reads local Claude Code, Codex and Hermes sessions, finds repeated failures and stages fixes for manual review

CLIExtended access73Repository stars

Agent session history is linked to Git commits so a change can be traced to its original prompt, conversation and affected files.

CLIExtended access5.3KRepository stars

The ee CLI gives agents durable local memory: rules, decisions and anti-patterns with scores and provenance

CLIExtended access76Repository stars

Intent CLI keeps the goal, the latest verified checkpoint and decisions in the project so a new agent session can resume

CLIExtended access266Repository stars

A CLI and skill that gather coding-agent session history into one SQLite file the agent can search for past decisions

CLIExtended access922Repository stars

README in short

The README describes ctx as a fast tool for searching coding-agent session history already on the machine. It installs with a single script, with options via GitHub Releases, mise, Homebrew and a source build. It lets you find an event, open a session and get JSON output, and wire skills and plugins into agents. Written in Rust, Apache-2.0 licensed.

README badge

Report a problem