Problem
Operator often has things to say to a specific agent that aren't yet ready to send -- mid-thought additions, things waiting on the agent to finish its current turn, things you want to remember to mention later. Right now they either get sent prematurely (and disrupt the agent) or get lost.
This is not the queue (which is "send these in order"). It's a scratchlist -- "I want to say this eventually but not yet."
Proposal
Add a per-session scratchlist:
- Small panel on each session page (collapsed by default), separate from the message composer and the queue.
- Operator types into it; entries persist locally (per session, per browser).
- Entries are NOT sent to the agent. Pure operator-side notes.
- From the scratchlist, the operator can:
- Promote to composer -- copies into the composer for editing + sending
- Promote to queue -- moves into the existing send-queue
- Delete -- gone
- Survives reload (localStorage minimum; ideally synced to hub so it's available on other devices).
Acceptance
Notes
- Think of it as a
git stash for messages.
- The queue is the conveyor belt; the scratchlist is the workbench.
- See also: related (filed) bug -- queue items getting consumed but not removed, session
7d706262.
Problem
Operator often has things to say to a specific agent that aren't yet ready to send -- mid-thought additions, things waiting on the agent to finish its current turn, things you want to remember to mention later. Right now they either get sent prematurely (and disrupt the agent) or get lost.
This is not the queue (which is "send these in order"). It's a scratchlist -- "I want to say this eventually but not yet."
Proposal
Add a per-session scratchlist:
Acceptance
Notes
git stashfor messages.7d706262.