Every AI coding agent forgets everything when the session ends. That’s the problem every “agent memory” tool is trying to solve — but they solve it in fundamentally different ways, and the differences matter more than the shared goal.
I run Vestige as my memory system, so I have a strong opinion on this space. When I looked at three newcomers — Pond, ai-memory, and Engram — the first thing that struck me is that they’re not actually competitors. They’re three different answers to three different questions, and only one of them is trying to do what Vestige does.
I wrote this survey for work. The goal wasn’t to win a tool-bake-off or prove a pet stack was superior — it was to answer one honest question: how do the people I build with actually spend their days with AI?
Every section maps to a layer of the modern dev toolchain. If you’re assessing a team’s workflow, onboarding new people, or just want to see where you sit relative to your peers, steal it. It’s licensed by the human copyright office of “you can just use this.”
There’s a whole category of open-source tools now that are all trying to be the minimal terminal coding agent — a small, fast, self-contained harness you run in your shell instead of a heavyweight IDE-integrated tool. They look nearly identical from the outside: type a prompt, watch the agent read files, run commands, and edit code.
But underneath, they’re chasing five different questions. This is a comparison of Ante, Crow, Maki, 3code, and Hax — five agents in that same space, and an honest look at which ones are genuinely different versus which are just the same idea wearing different languages.
Links & Stats
👉 https://github.com/caronc/apprise
Every service you touch has its own way of pinging you. Telegram has a bot API, Discord has webhooks, Slack has incoming hooks, Gotify has its own thing, and ntfy — the one you actually like — has a REST endpoint. Wiring each one into your scripts, cron jobs, and monitoring means learning N different APIs and maintaining N different code paths.
You trust your AI agent with your repo. Do you trust it with your SSH keys, your ~/.aws, your dotfiles? Most people running Claude Code, Codex, or OpenCode don’t think about it until it’s too late — and by then the agent has already read everything it could reach.
Greywall (Apache 2.0, Go) is a container-free, deny-by-default sandbox built specifically for AI coding agents on Linux and macOS. No Docker, no VMs — kernel-enforced isolation via Bubblewrap namespaces, Landlock, Seccomp BPF, eBPF monitoring, and a TUN-based network capture.
Every few weeks a new AI gateway appears on my radar, and every one tells the same seductive story: “Stop paying too much for LLMs. One endpoint, adaptive routing, zero markup. You’ll cut your bill 40%.”
I keep almost believing it. Whenever I do, I pull the price sheets — not the homepage claims, the per-token numbers. That exercise keeps saving me from a mistake, and it’s a repeatable enough pattern that it’s worth writing down. If you run any kind of LLM routing layer, you’ve probably heard this pitch and wondered if you’re leaving money on the table.
Two open-source projects are fighting for the same job — “make my AI agents work together instead of in parallel silos” — but they come at it from opposite poles. hcom is a peer-to-peer messaging bus: a chatroom where every agent is an equal. ORCH is a hierarchical orchestration engine: a company where every agent has a role, a manager, and a mandatory review gate. Same problem, opposite philosophies.
Full disclosure up front: I’ve contributed to hcom’s ACP integration (so Hermes can join the bus), so I’m not neutral on that one. All numbers below were fetched from GitHub at publish time.
Two open-source tools want to run a team of AI coding agents in parallel, but they pick opposite homes. ORCH is a terminal-native CLI that turns your repo into a mini software company — a CTO agent decomposes goals, engineering agents implement in worktrees, QA auto-verifies, and a reviewer gates merges. Kandev is a self-hosted web workspace — a kanban board wrapped in an IDE where you stay in control of every review gate. Same “orchestrate several agents” pitch, radically different answers.
The ecosystem has a real whiff of 2015’s microservices gold rush about it. A new “agent orchestrator” ships every week, each one claiming to be the control plane you’ve been waiting for, and almost all of them solve a problem that three other tools already solved last month. andyrewlee/awesome-agent-orchestrators is a genuinely good map of the chaos — 200+ projects, curated with real editorial taste, and organized not by star count but by the job each tool does. That last part is rarer than it should be.
Two open-source multi-agent orchestrators are fighting for the same job — “manage several AI coding agents from one place” — but they come at it from opposite directions. Kandev is a review-first development workspace wrapped around a kanban board. Omnigent is a policy-and-sandbox framework that treats every agent harness as a swappable driver. Same problem, totally different philosophies.
Full disclosure up front: I already run Kandev on my dev box, so I’m not neutral here. All numbers below were fetched from GitHub at publish time.
