Alternatives
Products that do what I built a RAG and knowledge graph agent that runs locally does
Claw-Coder is an AI agent that runs locally on your laptop and has access to powerful tools instead of configuring claude or codex to use a local model just use claw-coder. Why was claw-coder created? Answer: To solve the problem of privacy and security. When you use an agent that is configured with a cloud model like codex, cursor, Claude etc. You are not just getting the agent but you are giving up your codebase to train an llm which is a bit concerning and this reduces trust in the technology called AI but now another problem comes in performance when you switch to a local model that is…
- 1IB
Claw-Coder is an AI agent that runs locally on your laptop and has access to powerful tools instead of configuring claude or codex to use a local model just use claw-coder. Why was claw-coder created? Answer: To solve the problem of privacy and security. When you use an agent that is configured with a cloud model like codex, cursor, Claude etc. You are not just getting the agent but you are giving up your codebase to train an llm which is a bit concerning and this reduces trust in the technology called AI but now another problem comes in performance when you switch to a local model that is…
May 2026
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19CA
Clawlet is a personal AI agent that ships as a single, self-contained binary. No runtime, no package manager, no external database. The main thing that sets it apart: built-in hybrid semantic memory search (vector similarity + full-text) using a bundled SQLite with vector extensions. The index is just a local .sqlite file — no separate vector DB to run. Drop the binary on any machine and memory search just works. GitHub: https://github.com/mosaxiv/clawlet
Feb 2026 · github.com
- 20CO
So I've been building ClawMem, an open-source context engine that gives AI coding agents persistent memory across sessions. It works with Claude Code (hooks + MCP) and OpenClaw (ContextEngine plugin + REST API), and both can share the same SQLite vault, so your CLI agent and your voice/chat agent build on the same memory without syncing anything. The retrieval architecture is a Frankenstein, which is pretty much always my process. I pulled the best parts from recent projects and research and stitched them together: [QMD](https://github.com/tobi/qmd) for the…
Mar 2026 · github.com
- 21LC
May 2026 · github.com
- 22MC
I got tired of coding agents that feel like IDEs in disguise. Slow to start, full of chrome, opinionated about where you work. So I built one that doesn't get in the way. It's called *mini-coder*. The command is `mc`. Tagline: Small. Fast. Gets out of your way. Oh — and it mostly wrote itself (with some help from me). --- ## What it is mini-coder is a terminal-native AI coding agent built on *Bun.js* — fast startup, native TypeScript, built-in SQLite, no ceremony. It routes to *Anthropic, OpenAI, Google, Ollama, and Zen* and auto-detects your provider from env vars. No config file to write.…
Mar 2026 · github.com
- 23FB
TLDR: made the first background coding agent that has an isolated workspace and runs locally Howdy - I’m Kevin, co-founder of Firebender, and we built the first background coding agent in android studio / Jetbrains! Why not just use Cursor background agents or OpenAI Codex? Both of these require setting up a cloud container and cloning your existing developer environment, and maintaining it. Then when you want to iterate on changes as AI inevitably makes a mistake, you either throw away the work, or have to pull down the branch and clean it up. This feels really clunky. With Firebender,…
2025 · youtube.com
- 24SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →