Alternatives
Products that do what Epho does
Run Claude Code, Codex or Opencode in cloud with your repo
- 1
- 2
- 3
- 4
- 5
- 6
- 7AS
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
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18PA
Hey HN, I'm Mo. I've been building Paseo, an open source environment for running Claude Code, Codex, and OpenCode across desktop, mobile, web, and CLI. It started last September as a push-to-talk voice interface for Claude Code. I wanted to talk to an agent while going on walks. Then I wanted to see what it was doing. Then text it when I couldn't talk. Then review diffs, run multiple agents, and manage work across machines. After a lot of iteration, it turned into a broader environment. The basic model is: - A daemon runs on your machine (MacBook, desktop, VPS, etc.). - Clients connect to it…
Mar 2026 · github.com
- 19
- 20PO
Hey HN, I'm Mo. I'm building Paseo, a multi-platform interface for running Claude Code, Codex and OpenCode. The daemon runs on any machine (your Macbook, a VPS, whatever) and clients (web, mobile, desktop, CLI) connect over WebSocket (there's a built-in E2EE relay for convenience, but you can opt-out). I started working on Paseo last September as a push-to-talk voice interface for Claude Code. I wanted to bounce ideas hands-free while going on walks, after a while I wanted to see what the agent was doing, then I wanted to text it when I couldn't talk, then I wanted to see diffs and run…
Mar 2026
- 21
- 22OA
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…
Apr 2026 · github.com
- 23CR
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
- 24CC
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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →