OpenCode logo

Run OpenCode in the Cloud using Ellipsis

Run OpenCode sessions in isolated cloud sandboxes with your repositories cloned in. Define the agent as code, trigger it from GitHub events, Slack mentions, or a schedule, and govern it with scoped permissions, hard budgets, and full session visibility.

Install on GitHub
Documentation
01

Every OpenCode session gets its own machine

Each session runs in an isolated cloud sandbox with your toolchain preinstalled and your repositories cloned in. Run ten OpenCode sessions against the same repo and they never block or contaminate each other.

Placeholder: a sandbox spawning with repos cloned and the toolchain ready

Isolated sandboxes with dependency installs cached

02

OpenCode starts working the moment something happens

Spawn sessions from GitHub events, Slack and Linear mentions, Sentry alerts, or a cron schedule. Work starts when the event fires, not when someone opens a laptop.

Placeholder: an event stream firing sessions: PR opened, Slack mention, cron tick

GitHub, Slack, Linear, Sentry, and cron triggers

03

Scoped credentials, hard budgets, full transcripts

Every session gets its own scoped GitHub token and runs under a hard spend cap. Every turn and tool call is recorded and searchable, so what OpenCode did is never a black box.

Placeholder: budget caps beside a searchable session transcript

Permissions, budgets, and a full audit trail