Cloud agents

Run Claude Code in the Cloud

The same coding agent your team runs locally, in isolated cloud sandboxes with your repos cloned and your toolchain installed. Sessions keep running after you close the laptop, and each one gets scoped credentials, a hard budget, and a full transcript.

ellipsis.dev@priya-shah in your-org

What are we shipping today?

JavaScript was built in 10 days. It now runs most of the visible internet. Sleep well.

Repository: your-org/web-repo
Agent: Default
Model: claude-opus-5
Start a cloud session…
+ New session
Reviewing the schedule-conflict rules in api-repo2 turns · 3.2k · $0.21 · 2m ago
Backfill the tip-pool report totals for June6 turns · 12.4k · $0.86 · 18m ago
Fix the flaky shift-trade webhook retries11 turns · 4.8k · $1.15 · 41m ago
Draft the unfilled-shift digest cron1 turn · 2.2k · $0.30 · 3h ago
Bump pnpm to 10 across the monorepo4 turns · 9.1k · $0.62 · 1d ago
↓/esc: sessions
01

Run sessions in parallel, each in its own sandbox

Each session gets an isolated sandbox with repositories pre-cloned and dependency installs baked into a cached image, so repeat sessions start in seconds. Parallel agents build and run the tests without touching each other.

sessions · runningone sandbox each
add rest-period warnings to the schedule editorrunning
session_7Hq2mX4p · web-repo$0.84
finish the shift-boundary validatorrunning
session_3Fw8dK1r · api-repo$1.12
migrate tip-pool reports to the new schemarunning
session_9Kt4vR7m · api-repo$0.61
fix the trade-conflict flake in CIrunning
session_2Bn8kL5w · api-repo$0.37
unfilled-shift digest copy changesrunning
session_5Xc1pT9j · mobile-repo$0.22

Isolated sandboxes with your toolchain installed, cached across sessions

02

Start from the terminal, the API, or the thread you are in

Start a session from the CLI, POST /v1/sessions from CI, mention @ellipsis on GitHub, Slack, or Linear, or let an event or a cron schedule start it. Every entry point produces the same governed session.

ways to start a sessionsame governed session
CLIagent session start "fix the trade-conflict flake" --watch
APIPOST /v1/sessions · {"config_id": "agent_x9Kd3Fq2", "prompt": "…"}
Mention@ellipsis why does the shift-trade test fail on Mondays?
Eventtrigger: react · sentry issue alert, PR opened, Linear issue
Scheduletrigger: cron · schedule: "0 13 * * 1-5"

One session model behind every entry point

03

Scoped credentials, hard budgets, full transcripts

Every session gets its own GitHub token, scoped to the repos and permissions you grant and expiring in an hour. Spend runs under hard caps, and every turn and tool call lands in a transcript the whole team can search.

Sandbox credentialssession #1842
GH_TOKEN
scoped to web-repo, api-repo
ANTHROPIC_API_KEY
synthetic key, valid for this session only
ELLIPSIS_API_TOKEN
scoped to this session
All credentials revoked at teardown

Permissions minted per session, spend capped before compute starts

Frequently asked questions

You can use Ellipsis for...

Every use case runs on the same platform. See how it works