flower
/
All briefs
idea draft note thedarkroom_automation

Let's fix the Auto-Resolve buttons on the error message output on the

Dispatch

canonical · plan

Spec

markdown

hand-off · dispatch

Dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

kind

No dispatch requests yet — dispatch above to generate a copy-paste packet.

provenance · append-only

Trace

live
or paste a screenshot uploading…
  1. note added 4d ago

    Let's fix the Auto-Resolve buttons on the error message output on the /log view for orders so that each button press isn't blocking on the page, or causing a whole page reload or whatever we need to do. It feels super clunky in use where you click and then want to click the next one and it's blocking, nothing happens when you click and then the whole page reloads presumably because the first one you clicked came back with a response, etc, etc. Can we make this async and able to have more than one request in the air at a time?

    operator · operator:mike
  2. participant joined 4d ago
    system · operator:mike

epic · dependencies

Relationships

epic parent

depends on

No dependencies — dispatchable once planned.

agents · waves

Participants

  • operator:mike participant · active

trace · graph

Links

No links yet — they accrue as agents work the brief.

scope

Projects

  • thedarkroom_automation · primary

dogfood · read-only

Agent’s-eye view

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