Skip to main content
Coming soon. Current thinking, not a shipped contract. Today you start a session with POST /sessions and steer it with POST /messages; triggers add an event-driven way to do the same.
Triggers let external events start and resume sessions without an API call. You declare them on an agent; the platform receives the events and routes them to the right session. 
[[triggers]]
type = "github"
on   = "issue.labeled:agent"
  • Sources (planned): GitHub (issue labeled, PR/issue comment) and a Slack @mention. cron, http, and email are further out.
  • Routing: a routing key groups events into sessions — by default one session per issue; a comment on a PR the agent opened resumes the session that opened it.
  • Who can trigger: restricted to members of your organization by default, configurable per agent.

​
Connections

Triggers, and the deliveries that carry work back out, run through connections — integrations the platform operates, so the agent holds no tokens. Installing the OpenComputer GitHub App is the whole GitHub integration; a Slack connection powers the Slack channel. Model provider keys are connections too.

​
Deliveries

To act back on a source — open or update a draft PR, post a comment — the agent requests a delivery and the platform performs it, as the org or (with a personal grant) as the triggering user. Today the generic outbound path is webhooks; first-class GitHub/Slack deliveries are part of this work. See Channels for the two-way conversation model and Workspaces for the repo a triggered session works in.