Development
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.
Today
Yesterday
Reply to the agent...
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.
@ellipsis 100 req/min per key, 429 + Retry-After, Redis-backed
A labeled issue becomes a pull request
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.
What are we shipping today?
JavaScript was built in 10 days. It now runs most of the visible internet. Sleep well.
One command from the repo you are standing in
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.
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.00Prompt, trigger, repos, and caps in one committed file