Choose how agents respond in GitHub, Slack, and Linear, with their own instructions, environment, permissions, and budget. Sentry alert handlers are available by request.
Configure one handler per service and select the repositories, channels, teams, or projects it answers in. Give that responder a name, prompt, model, environment, permissions, and budget suited to the work.
Store each service’s handler file in your organization’s .ellipsis repository. The default-branch version is live. Invalid updates retain the last valid configuration and show a sync error, so a bad edit does not replace a working responder.
Open a handler to see its sessions, status counts, and accumulated cost. Set per-session and trailing budgets. Each attributed session keeps the handler identity and configuration revision that started it, even after the handler changes.
Save tasks, run on demand or with triggers
Run tasks and continue conversations
Reusable repositories, toolchains, and compute
Configure responders for mentions and alerts
Store credentials and select where they are used
Signed session notifications and delivery history
Frontier and open models, bring your own key
Transcripts, live streams, search, cost
Scoped credentials, SOC 2, audit trail
Hard caps per session, agent, and developer