AI · alternatives · 2026
24 alternatives to agentfdr
See why your coding agent looped, drifted, or burned tokens
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Agentmemory▲310Persistent memory for Claude Code, Codex & coding agents
May 2026 · agent-memory.dev · its alternatives →
- 2
AgenticLens▲64Visual debugging, tracing, and replay for agent workflows
Apr 2026 · agenticlens.in · its alternatives →
- 3
agentcad▲110A CAD design tool for coding agents (free + open source)
Jun 2026 · agentcad.dev · its alternatives →
- 4
Flare▲120The graph-first IDE and interactive map for agentic coding
Aug 2026 · github.com · its alternatives →
- 5
Replicas▲239Hey 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
AgentGrid▲77Hi 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 →
- 7
This project (Agents Observe) started as an exploration into building automation harnesses around claude code. I needed a way to see exactly what teams of agents were doing in realtime and to filter and search their output. A few interesting learnings from building and using this: - Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks - Hooks provide a lot more useful info than OTEL data - Claude's jsonl files provide the full picture - Lifecycle management of MCP processes started by plugins is a bit kludgy at best The biggest takeaway is…
Apr 2026 · github.com · its alternatives →
- 8
- 9
Claude Code as a Tech Lead with parallel Worker Agents
Apr 2026 · github.com · its alternatives →
- 10
built this because I got tired of re-teaching Claude Code the same context every session. Preferences, decisions, “we already tried X,” “don’t touch this file,” etc. After a few days it starts to feel like onboarding the same coworker every morning. Most “agent memory” tools auto-save everything. That feels good briefly, then memory turns into a junk drawer and retrieval gets noisy. Total Recall takes the opposite approach: a write gate. Before anything gets promoted, it asks one question: “Will this change future behavior?” If not, it doesn’t get saved. How it works: Daily log first (raw…
Feb 2026 · github.com · its alternatives →
- 11
VibeDrift▲28Your AI agent checks your codebase before it writes
Jul 2026 · github.com · its alternatives →
- 12
Hey HN, Claude Code is powerful, but its execution is a black box. You see the final result, not the journey. Agent Flow makes the invisible visible in realtime: - Understand agent behavior: See how Claude breaks down problems, which tools it reaches for, and how subagents coordinate - Debug tool call chains: When something goes wrong, trace the exact sequence of decisions and tool calls that led there - See where time is spent: Identify slow tool calls, unnecessary branching, or redundant work at a glance - Learn by watching: Build intuition for how to write better prompts by observing how…
Mar 2026 · github.com · its alternatives →
- 13
- 14WB
Hi HN — we built agentcall.dev because the coding agent you're already running in your terminal shouldn't be trapped there. The pitch: your existing Claude Code, Codex, OpenClaw, or Cursor session joins a Google Meet, Teams, or Zoom call as itself. Same session, same context, same file access. It speaks, listens, screen-shares a localhost webpage, and can code live while you all talk about what it's building. What's actually on the call: • Voice in, voice out. Two modes — collaborative (sub-second via a voice intelligence layer tuned for latency) or direct (~2s, your coding agent itself…
Apr 2026 · its alternatives →
- 15
Stop coding agents from wandering outside the ticket.
Jun 2026 · github.com · its alternatives →
- 16
See what your AI coding agents think, cost and do
Jul 2026 · tokentelemetry.com · its alternatives →
- 17
Usage, cost, and behavior tracking for AI coding agents
Jul 2026 · tokenbasehq.com · its alternatives →
- 18
ChatML▲12Cockpit for Claude Code - See everything your agents builds
Mar 2026 · chatml.com · its alternatives →
- 19
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 →
- 20
I finally got around to making a tool I've wanted for a long time: you can basically think of it as being "like Gmail for coding agents." If you've ever tried to use a bunch of instances of Claude Code or Codex at once across the same project, you've probably noticed how annoying it can be when they freak out about the other agent changing the files they're working on. Then they start doing annoying things, like restoring files from git, in the process wiping out another agent's work without a backup. Or if you've tried to have agents coordinate on two separate repos, like a Python backend…
Nov 2025 · github.com · its alternatives →
- 21IB
2025 · agentwrap.dev · its alternatives →
- 22
We were spending a lot of time re-writing the same primitives in projects we were doing getting claude + codex + other harnesses communicating in real time. Many other projects forced us into using their framework or harness or into a specific stack. So we open sourced an SDK that acts as the messaging layer without the rest of it. Still early, but we've been working on it and found it useful.
Jun 2026 · github.com · its alternatives →
- 23
Hi y'all. Been working on something that should've been made a long time ago imo. It compiles codebases into O(1) hashmaps that the agent queries to discover the structure of your code/answer questions/write code. It also does complete static analysis checks on any writes the agent makes. Don't take my word for it though. Here are the benchmarks: https://benzi.fly.dev/benchmark. on 2/20 tests, Claude Code (mostly Sonnet on one task) regressed or timed out. Benzi didn't because of course, it has a map it can query and not get lost in the sauce. On the other 18 it…
Aug 2026 · benzi.fly.dev · its alternatives →
- 24
Hi HN, AgentBox is an SDK for running coding agents (Claude Code, Codex, OpenCode) inside sandboxes (Docker, E2B, Modal, Daytona, Vercel). One API. Swap the agent or the sandbox and your code doesn't change. Think of it as what the AI SDK did for LLMs, but for agent + runtime. Most wrappers call agents in non interactive mode (claude --print, codex exec). AgentBox instead boots each agent's native server inside the sandbox (Codex app-server over JSON-RPC, OpenCode serve over HTTP/SSE, Claude Code's SDK WebSocket transport) and drives it from the host, behaving like an interactive…
Apr 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 →