Some steps in shipping software need judgment, not a script: triaging the failure, choosing the owner, deciding whether a change is safe. Spawn a background agent at that point with one API call. It reads the code, makes the call, and returns an answer your pipeline can act on, inside limits the platform enforces.
POST /v1/sessions is the whole integration: one HTTP call from a CI step, a deploy script, or your own service starts an agent session. Declare a structured output schema and the session must exit with JSON matching it, so the verdict feeds straight back into the step that asked.
curl https://api.ellipsis.dev/v1/sessions \
-H "Authorization: Bearer $ELLIPSIS_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"config_id": "agent_x9Kd3Fq2",
"prompt": "Candidate 1d40c7f is cut. Decide if it ships.",
"metadata": {"trigger": "release-gate"}
}'One request in, a typed verdict back
Its instructions, model, and environment live in one YAML file in your repository, live on merge. That includes the machine it runs on: append Dockerfile layers to install the tools the decision needs, a database client, a profiler, your own CLI, and they bake into a cached image.
ellipsis: version: v1 name: Release gate description: Decide whether a release candidate is safe to shipsession: claude: model: claude-opus-4-8 system: | Review every commit since the last release tag, run the migration checks, and decide whether this candidate ships. environment: repositories: - name: api-repo image: dockerfile_append: | RUN apt-get update && apt-get install -y postgresql-client setup: | cd api-repo && pip install -r requirements.txtInstructions, model, and machine in one committed file
Every session records its full log: each tool call, each turn, cost per step, downloadable as one file. Hard budget caps stop a runaway session cleanly, and the GitHub token is minted with exactly the scope the config grants, so a decision maker with read-only access cannot push, no matter what it decides.
session: permissions: github: permissions: read_only repositories: [api-repo] budget: session: 2.00 day: 20.00Budgets and permissions enforced by the platform