Development

Ship Features with Cloud Agents

Your laptop runs one agent at a time. Give each task its own sandbox with the code and dependencies ready, hand it off from the terminal or an issue, and get a pull request back. Permissions and budgets are set in YAML, and every session is logged.

your-org
New sessionK
Dashboard

Today

Yesterday

PS

Outbound webhook deliveries fail permanently on any non-2xx. Add retries with exponential backoff, max 5 attempts, and record each attempt.

Starting sandbox…
0s

Reply to the agent...

Send
01

Label an issue, get a pull request

Label an issue and an agent picks it up the moment it opens. It reads the surrounding code, follows the conventions it finds, can run the tests in its sandbox, and opens the pull request. Nobody copies the ticket into a prompt.

Issue #208 · api-repoClosed
Add rate limiting to API endpoints

@ellipsis 100 req/min per key, 429 + Retry-After, Redis-backed

Ellipsis
feat: rate limiting on API endpoints
PR #314 · 3 files · +187 −4
✓ checks passed

A labeled issue becomes a pull request

02

Hand off a task from your terminal

Run one command from the repository you are in and the agent takes it from there in a cloud sandbox. The session streams into your terminal, and you can close the laptop and come back to the result.

ellipsis.dev@priya-shah in your-org

What are we shipping today?

JavaScript was built in 10 days. It now runs most of the visible internet. Sleep well.

Repository: your-org/web-repo
Agent: Default
Model: claude-opus-5
Start a cloud session…
+ New session
Reviewing the schedule-conflict rules in api-repo2 turns · 3.2k · $0.21 · 2m ago
Backfill the tip-pool report totals for June6 turns · 12.4k · $0.86 · 18m ago
Fix the flaky shift-trade webhook retries11 turns · 4.8k · $1.15 · 41m ago
Draft the unfilled-shift digest cron1 turn · 2.2k · $0.30 · 3h ago
Bump pnpm to 10 across the monorepo4 turns · 9.1k · $0.62 · 1d ago
↓/esc: sessions

One command from the repo you are standing in

03

The agent doing the work is version controlled

Prompt, trigger, repositories, permissions, and spend caps live in one file in your repository. Creating or changing the agent is a pull request, live on merge.

agents/feature-builder.yamllive on merge
ellipsis:  version: v1  name: Feature builder  description: Implement the change described on the issuetrigger:  type: react  issue:    on: [opened]    labels: [agent]session:  harness:    type: claude_code    model: claude-opus-4-8  instructions: |    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.00

Prompt, trigger, repos, and caps in one committed file

You can use Ellipsis for...

Every use case runs on the same platform. See how it works