Run

You can close your laptop now

On the Ellipsis cloud, agents run in isolated sandboxes, so your code is secure and the whole team can see what they did. There is nothing to host and nothing to babysit.

Install on GitHubDocumentation

Cloud data flow

Events enter Ellipsis cloud, run in managed sandboxes, and return as GitHub code changes.

Developer Laptop

Spawn remote agent with @ellipsis

Slack

tagged in #engineering

GitHub

CI pipeline

Linear

Assigned to @ellipsis

Sentry

New error reported

Ellipsis cloud

Control plane

spawns runs, checks permissions, records status

Agent Sandboxes

ephemeral, scoped to single agent

SECURE

Agent Watchtower

streams every step, tracks budgets

GitHub

pushed

branch: ellipsis/fix-auth

commit: 8f3a1c9

pull request opened

Ellipsis backend writes the change back to GitHub.

splitshift-api #512 · Fix shift-trade raceIdle

pull_request_open · priya-shah opened #512

Reviewed the diff, flagged a double-booking window in trade_engine.py

2m 14s · $0.41

pull_request_push · priya-shah pushed 2 commits

Incremental review: the lock fix holds, one nit on the retry test

58s · $0.12

@ellipsis make the retry test cover shift boundaries · marcus-lee

Extended test_trade_retry with boundary cases, pushed 1 commit

1m 41s · $0.28

3 turns · one conversation per PRwakes on the next event

One conversation per PR

Agents that remember the whole thread

Every PR, issue, Slack thread, and Sentry alert is one durable conversation. Pushed commits get incremental review instead of amnesiac re-reviews, a reply wakes it in seconds with its working tree intact, and merge closes it. Idle time costs near zero.
agents/on-call-helper.yamldeployed on git push
triggers:  - type: cron    schedule: "0 14 * * 1-5"  - type: react    events:      - event: pull_request_open      - event: push        branches: [main, release/*]      - event: sentry_issue_alert  - type: mention    platforms: [github, slack]

Cron, events, mentions

Agents start themselves

Run on a schedule, react to 15 event types across GitHub, Linear, Slack, and Sentry, or start on demand from the dashboard, API, or CLI. Work starts the moment the event fires, while context is fresh.
splitshift-api #512 · comments

marcus-lee

@ellipsis use the staging database, not prod

👀 · conversation woken, same working tree

ellipsis[bot]

Switched the fixtures to the staging database and re-ran the suite: 12 passed. Pushed the change to this branch.

one message to steer, no kill-and-restart

@ellipsis

Mention it and it answers in the thread

Tag @ellipsis on GitHub, Slack, or Linear. It picks up the conversation it was mentioned in, takes the action you asked for, and answers in the same thread. It remembers the conversation, so 'now fix it' works.
agents/review-agent.yamllive on merge
ellipsis:  version: v1  name: Review agent  description: Review every PR, incrementally on pushclaude:  system:    file: .agents/prompts/review.mdtriggers:  - type: react    events:      - event: pull_request_open      - event: pull_request_pushsandbox:  repositories:    - name: splitshift-apilimits:  run: 2.00

Code review

Code review is an agent you define

Deploy a review agent in YAML: it reacts when a pull request opens, holds one conversation per PR, and reviews incrementally as commits land. Any coding agent can write slop; yours is the one that catches it before merge.

Explore the platform

Agents as code

Define in YAML, deploy with git push

Templates

Starter YAML templates for common tasks

Sandboxes

An isolated computer for every session

Observability

Observe and monitor fleetwide

Security & budgets

Boundaries up front, receipts afterward

Analytics

Engineering metrics for the age of AI

API & CLI

Everything the dashboard does, scriptable