Alternatives
Products that do what Smriti does
Git for reasoning state across coding agents
- 1
- 2
- 3GF
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
- 4
- 5
- 6AH
2025 · github.com
- 7
- 8
- 9
- 10
OSS IDE for controlling AI coding agents with built in loops
Jul 2026 · auravcs.com
- 11AK
I shipped a wiki layer for AI agents that uses markdown + git as the source of truth, with a bleve (BM25) + SQLite index on top. No vector or graph db yet. It runs locally in ~/.wuphf/wiki/ and you can git clone it out if you want to take your knowledge with you. The shape is the one Karpathy has been circling for a while: an LLM-native knowledge substrate that agents both read from and write into, so context compounds across sessions rather than getting re-pasted every morning. Most implementations of that idea land on Postgres, pgvector, Neo4j, Kafka, and a dashboard. I…
Apr 2026 · github.com
- 12
- 13
- 14EO
Hey HN! We’re Arne and Raban, the founders of Emdash (https://github.com/generalaction/emdash). Emdash is an open-source and provider-agnostic desktop app that lets you run multiple coding agents in parallel, each isolated in its own git worktree, either locally or over SSH on a remote machine. We call it an Agentic Development Environment (ADE). You can see a 1 minute demo here: https://youtu.be/X31nK-zlzKo We are building Emdash for ourselves. While working on a cap-table management application (think Stripe Atlas + Pulley), we found our development…
Feb 2026 · github.com
- 152C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 16
- 17
- 18
Stop re-explaining your project to every new AI chat.
21d ago · sulabhdubey.github.io
- 19
- 20
- 21
Your AI has your code's text, never its map. Fix that.
Jun 2026 · luuuc.github.io
- 22
- 23GW
I was frustrated with not being able to know why the code written by my colleague agents was in the codebase, so I build a tool to version agent trace along code in git.
Apr 2026 · hexapode.github.io
- 24OS
GitHub: https://github.com/ClioAI/kw-sdk Most AI agent frameworks target code. Write code, run tests, fix errors, repeat. That works because code has a natural verification signal. It works or it doesn't. This SDK treats knowledge work like an engineering problem: Task → Brief → Rubric (hidden from executor) → Work → Verify → Fail? → Retry → Pass → Submit The orchestrator coordinates subagents, web search, code execution, and file I/O. then checks its own work against criteria it can't game (the rubric is generated in a separate call and the executor never sees it…
Feb 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →