nowfound

AI · alternatives · 2026

24 alternatives to Compactdiff – see what compaction dropped from an agent session

Snapshot, diff, replay and branch AI coding-agent sessions. Reads Claude Code / Codex logs natively. Redaction on by default. Pure stdlib. - mkmkkkkk/compactdiff

Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.

  1. 1

    See everything Claude Code hides from your terminal

    Feb 2026 · claude-dev.tools · its alternatives →

  2. 2

    Persistent memory for Claude Code, Codex & coding agents

    May 2026 · agent-memory.dev · its alternatives →

  3. 3
    Rudel▲94

    Claude Code & Codex session analytics for dev teams

    Apr 2026 · rudel.ai · its alternatives →

  4. 4

    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 →

  5. 5
    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 →

  6. 6

    Hi HN, I built this because I got tired of the Claude Code CLI hiding details from me. Recent updates have replaced critical output with summaries like "Read 3 files" or "Edited 2 files". To see what actually happened, I was forced to use `--verbose`, which floods the terminal with unreadable JSON and system prompts. I wanted a middle ground: *Full observability without the noise.* `claude-devtools` is a local Electron app that tails the session logs in `~/.claude/` to reconstruct the execution trace in real-time. *Unlike wrappers, it solves the visibility gap in your native…

    Feb 2026 · github.com · its alternatives →

  7. 7
    Flare▲120

    The graph-first IDE and interactive map for agentic coding

    Aug 2026 · github.com · its alternatives →

  8. 8

    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 →

  9. 9

    Hi HN, I’m Michael, I built AgentGrid with my friend Souren because we were tired of losing our coding sessions and couldn't keep track of what was actually being built across our many projects. Our approach was to use an infinite canvas desktop app for the TUIs we already know and love, mainly claude + codex. We drew inspiration from Figma and Railway. Overtime we added image nodes, notes, terminals, coding editors, source control, etc. I wasn't sure about it at first. It took me a month to give the first version Souren built a real try. What got me was an Apple System Update I've been…

    Jul 2026 · agentgrid.sh · its alternatives →

  10. 10

    Comment on your AI agent's code & collaborate on changes

    Jul 2026 · apps.mergeable.io · its alternatives →

  11. 11

    Visual debugging, tracing, and replay for agent workflows

    Apr 2026 · agenticlens.in · its alternatives →

  12. 12

    See why your coding agent looped, drifted, or burned tokens

    Jul 2026 · kamihork.github.io · its alternatives →

  13. 13

    Save tokens and extend your coding sessions.

    Jun 2026 · ctxsift.dev · its alternatives →

  14. 14

    I built a terminal diff viewer for a workflow I couldn't do comfortably with existing tools: reviewing AI-generated code changes without leaving the terminal session where the agent runs, annotating what needs to change, and feeding those annotations straight back to the agent. Plenty of diff viewers exist, and some can even feed notes back to an agent, but none of them fit that flow for me - they pulled me out of the terminal into a separate app, or the round-trip back to the agent was clunky. Revdiff is how I solved it. From a Claude Code session I type `/revdiff main` or just say…

    Apr 2026 · github.com · its alternatives →

  15. 15

    I love Claude Code but got tired of having nothing to do while I waited for sessions to finish, and managing multiple sessions on the command line was getting annoying and I kept losing track of the tabs. I originally built a quick and dirty version of this for my own use, but decided to polish it up and make it open source. The idea is that you should be able to do all your agentic coding without leaving the tool or needing to go back to a traditional IDE. You can view the diffs, run your program, and merge your changes back. I support OSX and Linux right now, but could add Windows support…

    2025 · github.com · its alternatives →

  16. 16

    Claude Code / Codex session metadata can actually tell a story about how you work with AI coding agents. 50 days ago we posted about analyzing 1.6k Claude Code sessions from our own team. Skills were used in 4% of sessions, 26% were abandoned early, and we had no real benchmark for what good looked like. Now across 20k+ sessions, we started looking at behavior patterns from derived session metadata: consistency, intensity, session shape, repo breadth, output, cost intensity, and model range. Nine archetypes fell out, which we turned into playful cards. We built a Spotify Wrapped meets…

    May 2026 · app.rudel.ai · its alternatives →

  17. 17

    I’ve been tinkering with what a “multi-agent IDE” should look like if your day-to-day workflow is mostly in terminal (Claude Code, OpenAI Codex, etc.). The more I played with it, the more it collapsed into three fundamentals: * A good TUI: Terminal is the center stage, with other stuff (CodeEdit, Diff, Review) baked on the side. I don’t like piping Agent’s output through some electron wrapper, here you get to run CC/Codex/Droid/Amp/etc directly. * Isolation: agents shouldn’t step on each other’s toes. The simplest primitive I’ve found is Git worktrees. It is not as…

    Jan 2026 · agentastic.dev · its alternatives →

  18. 18

    devnexus is an open-source cli that gives agents persistent shared memory across repos, sessions, and engineers. It maps out dependencies and relations at the function level, builds a code graph, and writes it into a shared Obsidian vault that every agent reads before writing code. Past decisions are also linked directly to the code they touched, so no one goes down the same dead end twice. Still building it out but I would love to hear any thoughts/feedback

    Apr 2026 · github.com · its alternatives →

  19. 19

    Hey HN, I think session transcripts written by coding agents like Claude Code and Codex are very interesting because they offer a detailed window into how work gets shipped. You can see the sequence of decisions that resulted in the final PR, what the agent got wrong, tools used etc. So I built a cli that analyzes these sessions and provides a local dashboard that shows what each session shipped (PRs, features), how much each PR cost, and recommendations for more effective usage. Concretely, it enriches each session with: - Outcome links: merged PRs, features shipped, files changed -…

    Jul 2026 · github.com · its alternatives →

  20. 20

    Tool-agnostic TypeScript library for observing coding agent sessions. Built-in Cursor provider, extensible to Claude Code, Codex, and OpenCode. - vtemian/agentprobe

    Mar 2026 · github.com · its alternatives →

  21. 21
    Vexp▲14

    I built vexp because AI coding agents have two expensive problems: they waste tokens reading irrelevant code, and they forget everything between sessions. The token problem: agents read entire files linearly to build context. On a medium TypeScript project, a single query was consuming ~18k tokens — most of it irrelevant. vexp builds a dependency graph from the AST (who calls what, who imports what, what types flow where) and serves only the relevant subgraph as a token-budgeted capsule. ~2.4k tokens instead of ~18k, with better response quality because the context is precise. The memory…

    Mar 2026 · vexp.dev · its alternatives →

  22. 22

    I've been using Claude Code and Codex daily and kept losing track of which conversation was doing what across projects. So I built Claudine — a VS Code extension that reads your agent session files and renders them as a live kanban board. It auto-detects status, category, git branch, and error state. Everything syncs in real time, is searchable and drag-and-droppable. Cmd+Shift+K to open. No config, no backend, no accounts. It just reads the local session files your agents already produce. Open source, MIT licensed. Would love feedback — especially on what other agents you'd want supported.

    Mar 2026 · claudine.pro · its alternatives →

  23. 23

    Agents start blind every session. dizz gives them a memory.

    Aug 2026 · github.com · its alternatives →

  24. 24

    Every coding session in claude code/ codex starts blindly. It forgets the archiectural decisions you made in a session you ran yesterday/ a week ago or a month ago. We end up depending on maintaining a Claude.md file or diff markdown files that these agents rely on their memory features. I started building CogniKernel to solve this problem. Instead of relying on markdown memory files, CogniKernel observes the coding session itself. It captures decisions, constraints, architectural decisions, project specific context etc info as they naturally emerge. The goal is simple: The agent…

    Jul 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 →