Alternatives
Products that do what CTXD: Your files, any AI agent does
The context layer between your files and your AI Agents
- 1

- 2

- 3

- 4

- 5

- 6CS
Coding agents don't have long-term memory. But you do have months of full-fidelity agent transcripts stored on your machine. A simple solution that goes a long way: ingest those transcripts and logs into a structured SQLite database, then search them with ranked text match. Everything is fully local and doesn't require anything fancy like a graph database or hosted memory service. This is the idea behind ctx, a Rust CLI that handles the ingestion and searching. We give our agents a skill that tells them to reference past sessions before working in an area. Usually we do this through an…
Jul 2026 · github.com
- 7

- 8

- 9
- 10

- 11

- 12

- 13CA
ctx is a local SQLite-backed skill for Claude Code and Codex that stores context as a persistent workstream that can be continued across agent sessions. Each workstream can contain multiple sessions, notes, decisions, todos, and resume packs. It essentially functions as a /resume that can work across coding agents. Here is a video of how it works: https://www.loom.com/share/5e558204885e4264a34d2cf6bd488117 I initially built ctx because I wanted to try a workstream that I started on Claude and continue it from Codex. Since then, I’ve added a few quality of life…
Apr 2026 · github.com
- 14

- 15GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 16CA
Apr 2026 · ctx.rs
- 17

- 18

- 19
- 20
- 21

- 22

- 23AS
Hi, I am Bigyan from The Drive AI. We recently launched Chat Channels and Direct Messaging within The Drive AI. The Problem We're Solving: Current systems like Google Drive and OneDrive don’t utilize stored files to create new ones effectively. For instance, if you have a resume and a link to a job description, why can’t Google Docs write a resume for you? Team projects often involve file-specific tasks like reading or writing. However, existing team communication platforms, like Slack, result in inefficient communication due to their long threads of conversation. Have you ever posted in the…
2024 · thedrive.ai
- 24IB
TLDR; I built a tool that turns any API into a CLI designed for ai agents --- Got tired of dealing with bloated context windows from MCP servers and skills that stuff entire API docs into the agent's context CLIs fix this, agents run a single command to self-discover everything an API has to offer So, built a tool to generate them for any api. All CLIs are written in Go, fast and lightweight, no dependencies Help text (via the --help flag) is the killer feature: all context for each command/endpoint/parameter is extracted directly from the user-facing API docs and enhanced with…
Mar 2026 · instantcli.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →