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
Spawn an agent session on a cron schedule
Cron triggers: weekly digests, daily triage, dependency checks.
Spawn an agent session in response to Pull Request lifecycle events
Start sessions when pull requests open, push, merge, close, or get reviewed.
Spawn an agent session by mentioning @ellipsis
Route mentions on GitHub, Slack, and Linear to an agent.
Set up your agent's cloud development environment
Bake tools into the image, run setup hooks, and inject credentials.
Share skills across your team's agents and repositories
Repo skills load automatically; config skills share one library org-wide.
Spawn an agent session from the API and CLI
Trigger and watch sessions from the API and CLI.
Sync laptop Claude Code sessions into one searchable history
Bring laptop Claude Code sessions into one searchable history.
Attach agent screenshots to pull requests
Assets: images that outlive the sandbox, linkable on pull requests.
Concepts
How a session executes
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.
