Introduction
Deploy AI software engineers from YAML files in your repository.
An Ellipsis agent is a YAML file in your repository. It runs Claude in an isolated cloud sandbox with your repositories cloned and your GitHub, Linear, and Slack integrations connected, on a schedule, in reaction to events, on @ellipsis mentions, or on demand.
Quickstart
Three commands to a running agent. Full walkthrough in the Quickstart.
brew install ellipsis-dev/cli/agent
agent login
agent session start --template welcome-to-ellipsis --watchGet started
Quickstart
Install the CLI and run your first agent in three commands.
Your first agent
Write an agent config from scratch and deploy it from your repository.
Guides
Each guide solves one problem end to end, with a complete config and the output it produces. All guides.
How to automate your daily standup
A cron agent reads yesterday's merges and writes the summary itself.
How to review every pull request as commits land
Review each push as it lands, never re-commenting a reviewed line.
How to keep pull request descriptions up to date
Rewrite the description on every push, keeping the author's notes.
How to answer codebase questions from GitHub, Slack, and Linear
Ask where the work lives, answer from an agent with the code loaded.
How to turn Sentry alerts into root-cause diagnoses
Read the stack trace, find the code path, diagnose or open a fix.
How to give agents the tools and credentials your build needs
Bake tools into the image, run setup hooks, and inject credentials.
Concepts
Session lifecycle
The session lifecycle: statuses, steps, costs, and what each session records.
Budgets and spend
Per-session budgets, trailing spend limits, and per-developer limits.
The sandbox
The isolated environment agents run in, and how to detect it.
Agents as code
Why GitHub is the source of truth, and how sync works.
Analytics
Engineering metrics across humans, bots, and AI agents.