@agentskit/os-triggers (planned)
Trigger sources — cron, webhook, file, email, slack, github, linear, cdc.
Status: planned — Milestone M4. Distribution:
public(when shipped).
Wraps trigger sources behind a uniform contract. Every trigger feeds events onto the os-core bus and into matching flows.
Planned sources
cron— wall-clock and durable scheduleswebhook— signed HTTP callbacksfile— fs watchersemail— SMTP / IMAP (gap upstream — see ADR-0002 gap list)slack·discord·linear·jira·github— via upstream toolscdc— Postgres change data capture (gap upstream)
Why a separate package
Triggers are I/O-heavy and benefit from dedicated process / runtime
isolation. Splitting them keeps os-core zero-dep and lets users swap or
disable trigger sources independently.