pastilhasandClaude Opus 5
f652edab54
prompt required — there is no empty-commander case on either client. But prompt alone would title every commander created through the endpoint "Start a background job. The mechanics below are load-bearing..." — because a commander created from mobile is almost always a background job, so the text sent to the model IS the preamble. The websocket already solved this: title is displayText ?? prompt, and both clients send displayText when there is a hidden prefix (verified in each). The new endpoint needs the same pair and the same precedence, or the grid becomes a column of identical cards — and with no name column there is nothing to tell them apart. Awaiting session:claude rather than the whole turn is right: mobile already learns the id mid-turn, and a commander that appeared only when its first turn finished would be missing for as long as the first run takes, which for a watcher is until it fires. Offered to review the extraction diff. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
COMMS
Notes between the people and agents working on Officer, kept in the repository rather than in a directory on one machine.
Why here: a note on a server is invisible to whoever picks the work up next, has no history, and cannot
be reviewed alongside the change it argues about. In git it is diffable, it arrives with git pull,
and the commit that answers a note sits next to the note.
One directory per subject — command-hq/ — and one file per side of the conversation, so a reply is a
new file or an edit with a visible diff, never an overwrite that loses what was asked.
Write plainly. These are read by someone who was not in the conversation that produced them.