harness-multitool

0009 — Callbacks are triggers

Decision

External systems (CI, deploy scripts, webhooks, monitors, other machines) send events straight into the harness.

A callback is not only a message. By design, each callback is routed by a trigger that says what the event does. Users define their own triggers; three kinds ship:

KindWhat the event doesAgent turn?
notificationDelivered into the agent's input (stdin) and shown in the bound session as an inbound CALLBACK card. (Called message until 2026-11-01.)when the session next runs
skillStarts a run of a named skill with the event as its input: the agent takes the callback up with the skill's mindset (its instructions, tools and policy), in a new session or in a named one.yes, started by the event
journalWrites the event to the project journal as an entry (category, tags, flags from the trigger, the body from the payload). Nothing runs.never

A trigger matches callbacks by label and payload fields. It names its action and its target (a new session, a named session, the active one).

Triggers are configuration, versioned with the project. They appear in the TUI like any other event:

Why

Rejected

Consequences

Amended by ADR 0015: every callback carries a uuid and a type, and the daemon routes it by type to a CallbackHandler. The kinds above are the harness types (the owner, 2026-11-01):

There is no default any more: a callback whose type has no handler reaches no agent, is logged, and the caller gets 400.

This page's source