flower
/
All briefs
planned draft note flower blocked

Direct dispatch v2 — new-worktree + new-agent + Solo-project creation

canonical · plan

Spec

markdown

hand-off · dispatch

Dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

Blocked — dispatch is gated

Waiting on 1 unfinished dependency. Complete or cancel it to dispatch.

provenance · append-only

Trace

live
or paste a screenshot uploading…
  1. link added 1d ago
    agent · flower-refine
  2. link added 2d ago
    agent · flower-refine
  3. link added 2d ago
    agent · flower-refine
  4. status change 2d ago
    agent · flower-refine
  5. dependency added 2d ago

    Now depends on #103 (Verify direct-dispatch v1 (#36) works end-to-end).

    agent · flower-refine
  6. plan proposed 2d ago

    ## Goal The v2 of direct dispatch (#36): add the **creation flows** deferred from v1 — dispatch a brief to a NEWLY-created agent and/or a NEWLY-created worktree, from the brief detail. ## Depends on #103 (v1 verification) — blocked until v1 is proven working Rides on #22's `SpawnDaemonBridge` (spawn a new agent of a chosen harness) + worktree-manager. ## Scope 1. **New agent.** From "Dispatch direct", an option to spawn a NEW agent of a chosen harness (Claude/Codex/etc.) in an existing worktree and task it with the brief (reuses #22 SpawnDaemonBridge / solo-cli spawn). 2. **New worktree → Solo project → agent.** Create a NEW worktree from a chosen base branch, give it its own Solo project, spawn an agent in it, and task it — the full "worktree → solo project → spawn agent → task it" flow from the original #36 note. Operator chooses the base branch. 3. **Worktree grouping in the picker.** The selector shows worktrees + their agents (extends v1's grouped view) so it's clear which worktree a brief is dispatched to. 4. Same provenance as v1: record a `dispatch_request`, notify an active orchestrator via inbox. ## Acceptance - Operator can dispatch a brief to a new agent and/or a new worktree (with its own Solo project) from the brief page, choosing harness + base branch. - Tests with a faked spawn/worktree seam (no live spawn in CI). `php artisan test` green + pint. `Brief: #104` trailer. ## Provenance Chained v2 of #36 (operator, 2026-07-01), gated behind the #103 v1-verification. Rides on #22 (SpawnDaemonBridge) + worktree-manager. Created + chained by flower-refine (2026-07-03).

    agent · flower-refine
  7. note added 2d ago

    Chained follow-up to #36 (direct-dispatch v1), blocked on the v1-verification brief. Adds the creation flows deferred from v1: create a NEW agent of a chosen harness (reuses #22 SpawnDaemonBridge); create a NEW worktree from a chosen base branch → Solo project → spawn agent → task it (worktree-manager integration). Per operator's #36 answer (2026-07-01). Full spec via brief_update_spec.

    agent · flower-refine
  8. participant joined 2d ago
    system · flower-refine

epic · dependencies

Relationships

epic parent

depends on

agents · waves

Participants

  • flower-refine participant · active

trace · graph

Links

  • Scratchpad #378 execution
  • Scratchpad #375 execution
  • Scratchpad #364 execution

scope

Projects

  • flower · primary

dogfood · read-only

Agent’s-eye view

The literal recall_brief payload an agent gets — same service path as the MCP tool.