Event trigger

Core idea

Event triggers run in parallel with Cron: both deliver into Sessions; Agents decide everything from prompts:

Rendering diagram…

The trigger layer does not encode “review vs notify vs report”—Agents are the logic layer; user prompts are the configuration; triggers only deliver.

Event sources

Source	Typical use
Webhook	GitHub / GitLab / Gerrit / DOORS callbacks
Channel messages	Feishu / WeCom groups, new mail
Hook internals	Other Sessions’ Agent lifecycle events
Cron	Time-based (sibling subsystem)
Compound	Multi-source conditions (e.g., PR opened and CI green)

Flow

Rendering diagram…

Features

MySQL persistence — recover after restart
Debounce — suppress duplicate fires
Conflict policy — queue / skip / parallel
Chain trigger — one event fans into follow-on triggers

Typical setups

“Review every PR”        → PR Webhook → Session → code-review Skill
“Test on push to main”   → push event → Session → test Skill
“Notify on DOORS change” → DOORS Webhook → Session → impact analysis