trigger_flight MCP tool - Murmur

Remote-only. Selects and dispatches a flight for a trigger class and returns an acknowledgement identifying the spawned agent and resolved workspace. It does not wait for the agent to finish. To run a named flight directly, use spawn with flight instead.

Example

{
  "trigger": "task_delegation",
  "description": "Fix the flaky integration test and open a pull request.",
  "slug": "fix-flaky-test",
  "workspace": "backend",
  "repos": [{"clone_url": "https://github.com/example/backend"}],
  "out": "pr"
}

Parameters

Field	Required	Meaning and omitted behavior
`trigger`	Yes	Caller supplies `task_delegation`, the supported synchronous trigger class.
`description`	Yes	Caller supplies the task and context to compose with the flight’s prompt.
`slug`	Yes	Caller supplies a distinct agent name: 2–63 characters matching `[a-z][a-z0-9-]{1,62}`, excluding the `flight-` and `flightmsg-` prefixes.
`workspace`	No	Caller selects an authoritative workspace. Otherwise, resolution uses the winning flight’s workspace, repository matches, or Murmur’s selection. The acknowledgement reports the result.
`repos`	No	Repository objects with required `clone_url` and optional `base_branch`, `base_clone_url`, and `branch`, as on `spawn`. These also guide flight selection. The builtin task-delegation flight confines access to these repositories; omitting them grants it no repository access.
`out`	No	Expected output: `pr`, `push`, `respond`, or freeform instructions. Otherwise the flight decides; send `pr` when you need a pull request.
`completion_check`	No	`none` or `assessor`; otherwise the flight decides.
`on_idle`	No	`sleep`, `terminate`, or `keep_alive`; otherwise the flight decides.
`suggest_terminate_mode`	No	`suggest` or `immediate`; otherwise the flight decides.
`restrict_repository_access`	No	Adds repository confinement. Omitted or `false` never removes confinement imposed by the flight.
`followups`	No	Instructions by event class (`pr_merged`, `pr_comment`, `pr_review`, `ci_result`). Omitted classes keep the default or persona’s instructions.
`destination_url`	No	HTTPS lifecycle webhook destination. Omitted means no caller-supplied webhook.
`destination_events`	With destination	Subscription preset or classes, as on `spawn`.
`destination_context`	No	Opaque context echoed with webhook deliveries.
`signing_key`	With destination	Base64 HMAC-SHA256 signing key, supplied by the trusted webhook-configuring caller.

A running agent with the same identity is rejected; send it a follow-up with queue_add. A completed agent with that identity starts a fresh run.