Skip to main content
Labs preview. Triggers are not part of the stable Durable Sessions API. For stable API access, use POST /sessions to start work and POST /messages to steer it.
Triggers let external events start or resume sessions. You declare them on an agent; OpenComputer receives events, de-duplicates them, and routes them to a session.
  • Sources: GitHub (issue labeled, PR/issue comment) and Slack @mention.
  • 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.
To fire an agent on a cron rather than an external event, use Schedules — a time-based trigger with its own stable API.

​
Integrations

Triggers and outbound deliveries run through platform integrations, so the agent holds no GitHub or Slack tokens. Installing the OpenComputer GitHub App configures GitHub access; Slack channels use a Slack integration.

​
Deliveries

To open or update a draft PR, post a comment, or take another external action, the agent requests a delivery and OpenComputer performs it as the org or as the triggering user, depending on the configured grant. For generic outbound delivery, use webhooks. See Channels for the two-way conversation model and Workspaces for the repo a triggered session works in.