Introduction

What is Ellipsis

Ellipsis runs coding agents in isolated cloud sandboxes, with your repositories cloned and your GitHub, Slack, and Linear integrations connected. An event fires, an agent wakes up, reads the code, does the work, and delivers a real artifact: a pull request, an answer in the thread that asked, a report of the week's merged work. Then it shuts down, and the full session is there to inspect.

The two products

Cloud Agents are agents you define. Each is one YAML file: a trigger, a model, and a prompt. Triggers are a cron schedule, a GitHub, Linear, Sentry, or Slack event, or an @ellipsis mention; an agent with no trigger runs on demand. Splitshift runs one on a Monday-morning cron that summarizes the week's merged work across splitshift-web and splitshift-api.

Code Review reviews every pull request as commits land and posts findings as inline comments. One org-wide toggle turns it on, no YAML required. An optional pipeline file scopes which PRs get reviewed or replaces the reviewers.

How you interact

Agents are YAML files in your repository. The version on your default branch is the live agent: merge a change and the agent updates, with no deploy step. Agents as code explains the model.

Watch and control everything from the dashboard at app.ellipsis.dev, the agent CLI, or the REST API: start sessions, stream their steps, read history.

Start here

• Building agents: the Cloud Agents quick start installs the GitHub app, commits your first agent, and runs it.
• Reviewing pull requests: the Code Review quick start flips the toggle, then you push a commit to an open PR and watch the review land.