Ellipsis runs the coding agent your team already uses, on any model, in isolated cloud sandboxes with your repos cloned and your toolchain installed. Sessions survive the closed laptop, credentials are minted per session, spend is capped, and every step is recorded. It is the upgrade path from one agent on one machine to a governed fleet.
What are we shipping today?
JavaScript was built in 10 days. It now runs most of the visible internet. Sleep well.
Every session gets its own GitHub token, scoped to the repos and permissions you grant and expiring in an hour, plus an API token scoped to that session. Spend runs under hard caps per session, per agent, and per developer. No standing credentials, no surprise bills.
Permissions minted per session, spend capped before compute starts
Each session runs in its own isolated sandbox with repositories pre-cloned and dependency installs baked into a cached image, so repeat sessions start in seconds. Parallel agents spawn the full stack and run the tests without clobbering each other.
Isolated sandboxes with your toolchain installed, cached across sessions
Watch any session live, or answer which agent session produced PR #123 months later. Every turn, tool call, and thinking block lands in one transcript the whole team can search, and the exact instructions each run launched with are auditable next to what it did.
Transcripts outlive the sandbox
Start a session from a terminal, POST /v1/sessions from CI, mention @ellipsis on GitHub, Slack, or Linear, or let a Sentry alert or a cron schedule start it for you. Every entry point produces the same governed session.
One session model behind every entry point
Prompt, model, sandbox, permissions, and budget live in one version-controlled file, deployed with git push. Your existing review process becomes the change-control process for your fleet.
ellipsis: version: v1 name: Feature builder description: Implement the change described on the issuetrigger: type: react issue: on: [opened] labels: [agent]session: claude: model: claude-opus-4-8 system: | Implement the change the issue describes. Read the surrounding code first, follow the conventions you find, and run the test suite before you open the pull request. environment: repositories: - name: api-repo budget: session: 2.00 day: 20.00Define once, governed everywhere
The managed layer around every session, so none of it is each developer’s job.
Every session gets its own Linux container. Parallel agents never share state.
The repositories the config names are checked out before the agent starts, with gh authenticated.
Dependency installs bake into a cached image, so repeat sessions start in seconds.
Minted per session with exactly the repos and permissions the config grants, expiring in an hour.
Stored values inject by name into allowed sandboxes and can never be read back out.
Per-session caps plus trailing limits per account, agent, and developer, enforced before compute starts.
Watch any session over a WebSocket with lossless resume, from the dashboard or the CLI.
Every turn, tool call, and thinking block is recorded and searchable by the whole team.
The complete history exports as first-party records, so audits read a ledger.
Re-run any session with its frozen original config, or override the model, budget, or prompt.
Open a real editor into a live sandbox to review the diff and run tests where the agent worked.
Sessions can exit through your JSON schema, so pipelines get typed data instead of prose.