Deploy agents for feature development, code review, and more. Each agent gets an isolated sandbox, scoped permissions, and hard budget caps. Full observability included. Get started with a $100 credit.
Claude
Codex
GeminiTrusted by 400+ engineering teams
One command from the repository you are standing in. The agent gets its own sandbox, runs your suite, and opens the pull request.
$ agent session start "add rest-period warnings to the schedule editor" --watch
using config "Feature builder" (repo default)
session_7Hq2mX4p · sandbox ready in 8s · splitshift-web cloned
● Read src/schedule/editor.tsx
● Grep "restPeriod" (14 matches)
● Edit src/schedule/rest-period.ts
● Edit src/schedule/editor.tsx
● Bash (npm test)
⎿ Tests: 214 passed, 214 total
✓ opened PR #514 · 6 files · +212 −18
session_7Hq2mX4p · 9 turns · 88.4k tokens · $0.94
The prompt, the model, and the repositories it watches live in one file you own.
Combinator
ellipsis: version: v1 kind: code_review name: Code reviewpull_requests: repositories: [splitshift-web]review: - name: correctness claude: model: claude-opus-4-8 system: | Flag correctness bugs and unhandled edge cases. Fix on the exact line.budget: run: 10.00Describe the rule and pick when it fires. Path filters mean the agent only wakes up on the pull requests it applies to.
“Make sure every pull request that changes the frontend has a screenshot of the change.”
● Bash (npx playwright screenshot)
⎿ schedule-editor.png · 1440×900
✓ commented on #518 · $1.42
ellipsis: version: v1 name: Screenshot checkclaude: model: claude-haiku-4-5-20251001 system: | Start the dev server, open the affected page with playwright, and comment with the screenshot.trigger: type: react pull_request: on: [opened, pushed] repositories: [splitshift-web] paths: ["src/**/*.tsx"]sandbox: repositories: - name: splitshift-web image: setup: | cd splitshift-web && npm install npx playwright install --with-deps chromium github: permissions: contents: read pull_requests: writebudget: session: 3.00The platform
From the YAML that defines an agent to the audit trail it leaves behind.
Why do agents need a cloud? →Latest
Ellipsis started in 2023 reviewing code and fixing bugs. Today we run managed coding agents: defined in your repo, deployed with git push, governed with permissions, transcripts, and hard spend caps.
Read post →The future of software is agents defined in code: versioned behavior, isolated cloud sessions, scoped permissions, and human judgment at the checkpoints that matter.
Read post →What we learned shipping autonomous coding agents to hundreds of engineering teams. Sandboxing, context management, cost control, and the things that actually matter.
Read post →Write the config, push to GitHub, and Ellipsis handles the rest.