Skip to content

Execution Model

  1. Slack sends an event to /api/webhooks/slack.
  2. Junior validates and routes the event.
  3. Thread work is enqueued to junior-thread-message.
  4. /api/queue/callback processes queued work.
  5. Agent turn runs with configured tools, skills, and capability gates.
  6. Reply is posted back to the original Slack thread.
  • Avoids long-running webhook request paths.
  • Makes retries explicit and observable.
  • Preserves thread execution invariants in background turns.
  • Webhook ingress and queue callback are both required for production.
  • Tool/credential usage is capability-gated and requester-bound.
  • Failure states are logged and surfaced for operator recovery.