Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Search the coding agent history already on your machine
| Date | Stars |
|---|---|
| 2026-07-31 | 986 |
| 2026-08-02 | 999 |
| 2026-08-06 | 999 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
35.0
growth rate 0.00%/day
<img src="docs/assets/ctx-readme-banner.png" alt="You have months of coding agent history on your machine. Search it with ctx." width="100%"> ctx is an open-source CLI for fast local search across your past coding agent sessions. Coding agents usually start from zero. They can inspect the current repo, but they often cannot recover the discussions, decisions, failed attempts, commands, and test results from earlier work. Those sessions are full of useful context: - decisions, constraints, intent, and rejected approaches from you - bug investigations, refactors, file paths, commands, patches, and notes from previous agents ctx builds a local Tantivy search index from those logs, then gives current and future agents a CLI for finding the prior discussion, command, or failed attempt before they repeat it. ## Install and set up ctx macOS, Linux, and FreeBSD: ```bash curl -fsSL https://ctx.rs/install | sh ``` Windows PowerShell: ```powershell irm https://ctx.rs/install.ps1 | iex ``` or prompt your agent: ``` Please install and set up ctx CLI (see github.com/ctxrs/ctx) ``` ## 50x more token-efficient than raw transcript search By structuring agent history into sessions, events, metadata, and indexed fields, then returning ranked cited matches, agents can access meaningful history with far fewer tokens than raw search. Results vary by query and corpus, but raw search is often so token-heavy that it can be effectively the same as not having usable history. <img src="docs/assets/ctx-token-efficiency-chart.png" alt="Token output per agent history search: ctx search 917 tokens, raw transcript search 45,734 tokens." width="100%"> ## How it works Your past agent sessions remain in provider-owned history. ctx discovers supported sources and reads each provider's native format, including short read-only snapshots of provider SQLite databases. It publishes immutable Core/Tantivy generations containing complete policy-selected normalized records and stable provider/source identities. ctx is written in Rust. Lexical search and typed presentation read the local Tantivy generation under `search/lexical`; optional semantic search uses generation-bound flat-F32 data under `search/semantic`. The local daemon owns refresh and optional semantic indexing. Local Pro separately derives an encrypted facts graph from a pinned Core generation, and content-free local usage aggregates live in an independent `usage.sqlite` sidecar. The index is local and private by default. Transcript text is preserved rather than hiding local paths or secret-shaped strings, so review copied output before sharing it outside the machine. ```bash # Index all of your existing local agent sessions ctx setup # Your agent can search prior work with normal language ctx search "failed migration" # Search sessions/events that touched a file ctx search --file crates/foo/src/lib.rs # Or search multiple terms ctx search --term "failed migration" --term rollback --term "cursor rename" # Results include matching sessions, snippets, and ctx IDs # evt_01h... ses_01h... codex "migration expected the old cursor name" ... # Print the matching part of the old transcript ctx show event <ctx-event-id> --window 3 # Or print a compact transcript of the original session ctx show session <ctx-session-id> ``` Those IDs let your current agent recover as much context from previous sessions as it needs. ctx does not send your prompts, transcripts, or indexed history to a cloud service, call model APIs, require API keys, or write into your source repositories. The installed binary also includes local docs and man-page generation: ```bash ctx docs search "upgrade" ctx docs show cli-reference ctx docs man --print ctx ``` Official installer-managed binaries support signed self-upgrades: ```bash ctx upgrade status ctx upgrade check ``` Source builds and package-manager installs remain unmanaged and do not self-upgrade. For the full pipeline, see [How ctx works](https://ctx.rs/c
Excerpt of 7,856 characters
Read on GitHub
1.8k
13
8
5
Raúl
5
2
1
1
1
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:0ba28e1518032260, topic:agents, topic:agentic, topic:agentic-ai