Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Launching today
Epho
Run Claude Code, Codex or Opencode in cloud with your repo
179 followers
Run Claude Code, Codex or Opencode in cloud with your repo
179 followers
Epho runs claude code, codex, or opencode in the cloud. POST a message, stream back the work. no sdk, no daemon, no infra on your side. Epho manages the underlying sandboxes, fallbacks, event streaming, and agent configuration for you. With a single API call, you can easily launch a Claude Code session that is already connected to your repo, understands your context, and runs in a serverless sandbox.
The question I would want answered first is what happens to a long session when your platform ships.
We run browser agents in serverless containers, and the thing that took us longest to see was that our own deploy cadence was the biggest single source of failures. A run took about 35 minutes. Any merge to main rolled the fleet, and we were merging roughly every 23 minutes. So a real share of runs were being evicted mid-flight by us, not failing on their own merits. The logs just showed the work stopping.
So, two things I would ask of any cloud agent runtime: does a rollout drain in-flight sessions or kill them, and when a sandbox dies does the caller get a distinct signal for evicted versus the agent finishing badly? Those look identical from the outside and they need completely different responses.