Alternatives
Products that do what Open-agent-SDK – Claude Code's internals, extracted and open-sourced does
Claude Code's source map leaked last month. Instead of just reading it, I fed the entire source into Claude Code itself and asked it to extract the core agent loop logic. The result: open-agent-sdk — a drop-in replacement for claude-agent-sdk that's fully open source and doesn't spawn a CLI subprocess. Why this matters if you've built with claude-agent-sdk: claude-agent-sdk is just a thin wrapper around the Claude Code binary. It works, but it's a black box — when something breaks, you're stuck. Every query creates a new Claude Code process. That's fine on a laptop, not fine when you're…
- 1
- 2OS
2024 · github.com
- 3
- 4
- 5
- 6CCCode Claude Code▲117
In the nature of Open Source, I am releasing something I'm actively working on but is insanely simple and will likely be made anyways. It is an SDK for scripting Claude Code. It's a lightweight (155 lines) and free wrapper around claude code This is a big deal because it seems that using claude code and cursor has become largly repitive. My workflow typically goes like this: Plan out my task into a file, then have claude code implement the plan into my code. I'm actively building a product with this, but still wanted to make it OSS! Use it now with `pip install codesys`
2025 · github.com
- 71O
Hi, we're Sergey and Serafim. We've been building dev tools at 21st.dev and recently open-sourced 1Code (https://1code.dev), a local UI for Claude Code. Here's a video of the product: https://www.youtube.com/watch?v=Sgk9Z-nAjC0 Claude Code has been our go-to for 4 months. When Opus 4.5 dropped, parallel agents stopped needing so much babysitting. We started trusting it with more: building features end to end, adding tests, refactors. Stuff you'd normally hand off to a developer. We started running 3-4 at once. Then the CLI became annoying: too many terminals, hard to…
Jan 2026 · github.com
- 8
- 9AS
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
- 10GF
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
- 11RT
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
- 12
- 132C
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
- 14
- 15IB
Hi! My name is Herve Kom, a computer science student that is interested in learning new things everyday! As one of my graduation project, I have developed a Claude Code -like Coding CLI, but with enhancement for API Testing: - Auto-generate & run tests (unit, e2e, Playwright, CI/CD, etc.) - Say bye-bye to hallucinations with built-in MCP Server to let LLM directly read from API Docs - Adding Agent.md support for better context persistence across your whole codebase - Automatic bug & security scans (logic is kind of basic but works great!) - Vibes, I want it to feel less "enterprise" but…
2025 · github.com
- 161D
We just open-sourced the internal system we built at Assembled for running coding agents as a team. Coding agents worked well for individual engineers, but the surrounding workflow was a bit of a mess. We generally found that many engineers had different MCP connections and context for their agents, personal automations running that other people couldn’t access, and very little introspection for what a human’s input into the coding agent looked like. So we built an internal system that converted coding agents into shared team infrastructure. The system runs Codex, Claude Code, OpenCode, and…
Jun 2026
- 17MO
Why we built it: • Claude Code: great for coding, but no video/audio support, localhost only • OpenAI SDK: single-model, no native multimedia tools • Both: no integrated DevTools for debugging agent reasoning So, we built Mix as an alternative for multimodal applications. • Native video/audio/PDF analysis tools (via Gemini for vision, Claude for reasoning) • Multi-model routing instead of single-provider lock-in • One-command Supabase setup for cloud deployment (vs localhost-only) • HTTP architecture that enables visual DevTools alongside agent workflows • Go backend: 50-80%…
Oct 2025 · github.com
- 18
- 19CB
Clink lets you use the coding agents you already pay for (Claude Code, Codex CLI, Gemini CLI, Z.ai GLM) to build → live-preview → ship apps in an isolated container. No token purchases, no extra cost for coding. Just link your existing Claude/OpenAI/Gemini account and start building and deploying instantly. Why we built this: Claude Code is our go-to for coding, but it lacked preview + deploy capabilities. We didn't want to pay Lovable again just for that. Different agents excel at different tasks - Claude Code for versatility, Codex for complex work, GLM for speed. We needed one…
Oct 2025 · clink.new
- 20GC
As I started to use Claude Code to do more random tasks I realized I could basically build any CLI tool and it would use it. So I built one that controls the browser and open-sourced it. It should work with Codex or any other CLI-based agent! I have a long term idea where the models are all local and then the tool is privacy preserving because it's easy to remove PII from text, but I'd definitely not recommend using this for anything important just yet. You'll need a Gemini key until I (or someone else) figure out how to distill a local version out of that part of the pipeline. Github link:…
2025 · cli-agents.click
- 21AF
Hi guys, I've been using Claude Code for almost everything lately. Have given one an email account so it can research business leads, draft emails, fact-check them and clear them with me before sending (works really well by the way). I also tend to have a few Claude Code agents running at any one time for coding. I used to create a split terminal to manage them from there, but found working in the terminal all day pretty depressing and, more importantly, found it hard to follow Claude Code's process and see which agents needed my immediate attention. I tried Anthropic's VS Code Claude Code…
Jul 2026 · abralo.com
- 22
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…
29d ago · benzi.fly.dev
- 23OO
One coding agent orchestrator UI for Claude and Codex, but actually feels nice. Free, open-source, MIT licensed. Why I built it: - I wanted a lightweight UI as nice as the Codex app, but without the complexity and the custom diffs on the side - I want files and diffs open straight in my editor! - And I wanted both agents - Anthropic + OpenAI — in one place How it works: - No API keys, no OAuth, no separate billing — it just uses whatever you're already logged into. So your Claude Max and ChatGPT/Codex subscriptions both work out of the box. - Talks to Claude Code via the Claude Agent…
Apr 2026 · github.com
- 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 →