nowfound

AI · alternatives · 2026

24 alternatives to Ctx – a /resume that works across Claude Code and Codex

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…

Ctx is a local SQLite-backed tool for Claude Code and Codex that maintains persistent workstreams across coding agent sessions. It stores context including notes, decisions, todos, and resume packs, allowing users to… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Prices are shown for the 3 we have checked on their own sites, 3 of them free or with a free tier.

  1. 1

    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 · its alternatives →

  2. 2

    Run parallel coding agents from one desktop workspace

    Apr 2026 · claude.com · its alternatives →

  3. 3
    Rill Browserfree▲540

    The browser where Claude Code and Codex work beside you

    18d ago · rill.love · its alternatives →

  4. 4

    Store, review, and share your Claude Code sessions

    Mar 2026 · bench.silverstream.ai · its alternatives →

  5. 5
    ctx▲4

    Keep your AI coding sessions alive.Never lose context again.

    Jun 2026 · github.com · its alternatives →

  6. 6

    Let Claude use your computer from the CLI

    Mar 2026 · code.claude.com · its alternatives →

  7. 7

    Instant recall for coding agents. Search the history already on your machine. Git blame, but for agent sessions.

    Apr 2026 · ctx.rs · its alternatives →

  8. 8

    Hey HN! I built Retain as the evolution of claude-reflect (github.com/BayramAnnakov/claude-reflect). The original problem: I use Claude Code/Codex daily for coding, plus claude.ai and ChatGPT occasionally. Every conversation contains decisions, corrections, and patterns I forget existed weeks later. I kept re-explaining the same preferences. claude-reflect was a CLI tool that extracted learnings from Claude Code sessions. Retain takes this further with a native macOS app that: - Aggregates conversations from Claude Code, claude.ai, ChatGPT, and Codex CLI - Instant full-text…

    Jan 2026 · github.com · its alternatives →

  9. 9
    Termexo▲98

    A local Windows workbench for Claude Code and Codex

    Aug 2026 · termexo.com · its alternatives →

  10. 10

    I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…

    Dec 2025 · github.com · its alternatives →

  11. 11

    Persistent memory for AI coding agents

    Apr 2026 · contextpool.io · its alternatives →

  12. 12

    I got tired of sharing AI demos with terminal screenshots or screen recordings. Claude Code already stores full session transcripts locally as JSONL files. Those logs contain everything: prompts, tool calls, thinking blocks, and timestamps. I built a small CLI tool that converts those logs into an interactive HTML replay. You can step through the session, jump through the timeline, expand tool calls, and inspect the full conversation. The output is a single self-contained HTML file — no dependencies. You can email it, host it anywhere, embed it in a blog post, and it works on mobile. Repo:…

    Mar 2026 · github.com · its alternatives →

  13. 13
    PMB▲211

    PMB gives Claude Code, Cursor, Codex and Zed a real memory. Decisions, lessons and facts in one SQLite file on your disk. Offline, no API keys, no cloud.

    Jun 2026 · pmbai.dev · its alternatives →

  14. 14

    We built an open-source proxy that sits between coding agents (Claude Code, OpenClaw, etc.) and the LLM, compressing tool outputs before they enter the context window. Demo: https://www.youtube.com/watch?v=-vFZ6MPrwjw#t=9s. Motivation: Agents are terrible at managing context. A single file read or grep can dump thousands of tokens into the window, most of it noise. This isn't just expensive — it actively degrades quality. Long-context benchmarks consistently show steep accuracy drops as context grows (OpenAI's GPT-5.4 eval goes from 97.2% at 32k to 36.6% at 1M…

    Mar 2026 · github.com · its alternatives →

  15. 15
    Replicas▲239

    Hey HN! I'm Connor, creator of Replicas. I'm a heavy Codex/Claude Code user, and I wanted to hand off tasks to agents like I would to an engineer - kick something off before work, let it scaffold while I'm at lunch, even come back to a ready PR. The problem: existing alternatives use workspace VMs that are black boxes. I have no access to any of them - they can't run tests, read logs, or use tools like the Playwright MCP (which I use to verify agents actually fixed what they claim to fix). Replicas gives agents real cloud workspaces where they can: - Run your test suite and read the…

    Jun 2026 · replicas.dev · its alternatives →

  16. 16

    Hello everyone. Claudraband wraps a Claude Code TUI in a controlled terminal to enable extended workflows. It uses tmux for visible controlled sessions or xterm.js for headless sessions (a little slower), but everything is mediated by an actual Claude Code TUI. One example of a workflow I use now is having my current Claude Code interrogate older sessions for certain decisions it made: https://github.com/halfwhey/claudraband?tab=readme-ov-file#s... This project provides: - Resumable non-interactive workflows. Essentially `claude -p` with session support: `cband continue…

    Apr 2026 · github.com · its alternatives →

  17. 17

    Hi HN, we’re open-sourcing ktx. It’s an executable context layer that makes agents reliable on your data stack. We built it after going through the experience of building production-grade data agents for dozens of companies. If you’ve also tried building them, or simply tried using Claude Code or Codex on your data warehouse, you’ll know that accuracy is the #1 issue. Agents are great at generating valid SQL, but it’s not always correct SQL. To cite a few examples of “agents gone wrong”: - Stale column + hidden business rule: when preparing a board report, a finance analyst asks Claude Code…

    May 2026 · github.com · its alternatives →

  18. 18

    I built a tool that stores your full Claude Code history to let you easily find and resume sessions. It has TUI, CLI and MCP interfaces. It's a single Go binary, and the session history is synced to SQLite each time you use it. Default mode is the TUI with a session browser and full-text search. Once a session is selected you can browse and search within it, resume it or export to markdown. The MCP server provides tools to let Claude search back through the session for pre-compact context or pull from prior sessions. I use this constantly. I've seen elaborate continuity systems to give…

    Jan 2026 · github.com · its alternatives →

  19. 19

    Comprehensive memory management for Claude Code

    Mar 2026 · codeyam.com · its alternatives →

  20. 20

    AI powered cli coding agent that monitors your dev/test server and fixes errors and adds features - vysakh0/dravid

    2024 · github.com · its alternatives →

  21. 21

    i kept hitting rate limits in Claude Code mid-debugging, then hopping to Gemini or Codex. the annoying part wasn't switching tools (copy-pasting terminal output doesn't bring tool-use context with it) — it was losing the full conversation and spending 10 minutes re-explaining what i was doing. so i built *continues*. it finds your existing AI coding sessions across five tools (Claude Code, GitHub Copilot, Gemini CLI, OpenAI Codex, OpenCode), lets you pick one, and generates a structured handoff so you can continue in another tool without starting from zero. npx continues # interactive TUI:…

    Feb 2026 · github.com · its alternatives →

  22. 22
    Caudex▲94

    Terminal for Claude Code with GUI controls

    Feb 2026 · caudex.sh · its alternatives →

  23. 23
    Scapefree tier, from $9.99/mo▲59

    Hey HN, we've been using Claude Code daily for months, and built Scape to fix our biggest pain point: managing multiple worktrees quickly & reducing the mental load of switching between them quickly. What we built: Scape is a macOS menu bar app that sits on top of Claude Code and gives you: - One-click worktrees: click a button, get a new git worktree with a Claude session already working on it. Develop in parallel without leaving your current branch. - Toolkit: per-session actions like "Create PR", "Commit & Push", "Run & Fix Tests." Add your own with bash scripts or prompts. -…

    24d ago · scape.work · its alternatives →

  24. 24

    Claude Code is amazing for individuals but terrible for teams. I spent the last six months building my perfect mix of MCP servers, subagents, commands and skills. Claude Code writes 100% of the code now, but sharing this with my team? Painful. 1. Blog posts and workshops don't work (and don't scale) 2. Committing tools to N repos means N PRs. A tool changes? N more PRs. 3. Same tools, different files or folders for each AI assistant; not everyone uses Claude Code It is like 1999 all over again; FTPing files up to prod and versioning with ".bak" suffixes. So I built sx. It is your team's…

    May 2026 · github.com · its alternatives →

Also compare

Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →