Alternatives
Products that do what Replicas does
Run Claude Code and Codex in the cloud
- 1

- 2

- 3

- 4

- 5

- 6

- 7

- 8

- 9

- 10
- 11

- 12

- 13AS
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
- 14

- 15
- 16

- 17
- 18

- 19CC
I’ve found coding agents to be great at 1/ finding everything they need across large codebases using only bash commands (grep, glob, ls, etc.) and 2/ building new things based on their findings (duh). What if, instead of a codebase, the files were all your workplace docs? There was a `Google_Drive` folder, a `Linear` folder, a `Slack` folder, and so on. Over the last week, we put together Craft to test this out. It’s an interface to a coding agent (OpenCode for model flexibility) running on a virtual machine with: 1. your company's complete knowledge base represented as…
Jan 2026
- 20

- 21SR
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
- 22CR
Hey HN, Over the past 10 months I've been using Claude Code heavily, and one limitation kept coming up: you can really only run one coding agent at a time. While one agent is refactoring something, the rest of the repo is basically blocked unless you start manually juggling branches and working directories. The core issue is that AI coding agents operate directly in your filesystem. If two agents run in the same working directory they quickly start stepping on each other’s changes. Git worktrees turned out to be a surprisingly good primitive for solving this. So I built ChatML, a Desktop app…
Mar 2026 · github.com
- 23

- 24

Run, review, and remember work across AI coding agents
10d ago · agentos.aiutil.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →