The Claude Code GitHub Action runs an agent inside your CI pipeline. Ellipsis runs the same kind of agents as a managed service.
| Infrastructure to run it | Managed cloud sandboxes, nothing to host | You provision and maintain the CI runners and workflows |
| Startup time | Warm sandboxes in seconds, dependencies baked into a cached image | Every run boots a runner, checks out, and reinstalls dependencies |
| Triggers | Pull requests, pushes, cron, and @ellipsis in Slack and Linear | GitHub events inside your CI only |
| Scheduled agents | Native cron schedules | Scheduled workflows you build and maintain |
| Team-wide observability | Every session, cost, and diff in one dashboard | Scattered across workflow logs, one run at a time |
| Spend controls | Per session, day, week, and month caps, enforced live | You track API spend yourself |
| Permissions | Per-agent GitHub token scopes, enforced at the mint | Whatever the workflow and token happen to allow |
| Audit trail | Every action and every config version recorded | CI run logs, retained per your CI |
| Agent definition | One versioned YAML per agent, deployed with git push | Workflow YAML focused on CI steps, not the agent |
| Secrets | Central, write-only sandbox secrets store | GitHub Secrets, managed per repo |
| Isolation and retention | Ephemeral sandbox per session, zero source code retention | Depends on how your runner is set up |