Repository navigation
Show Inbox pictures and let the user answer from the page - #186
Merged
sreejithraman merged 1 commit intoNov 15, 2026
Merged
sreejithraman merged 1 commit into
sreejithraman merged 1 commit into
Conversation
Inbox items can carry pictures whenever a choice is visual: one per option, a side-by-side, a before and after, or a short sequence. Report asks and the new `picture` command copy them into the program's files/ under content names; the renderer stages them beside the page, and a tap opens each one larger in an in-page viewer. A record that names a missing picture fails the check. On a Claude artifact, Send answer saves the pick in the page database, which only the artifact's owner can read or write, keyed by decision and revision. It then offers a link to the coordinator's answer wake, a T3 webhook. `answer --stored` records each stored pick at its current revision with the pick as its source. A pick for an earlier revision never applies: it asks again, or becomes a reopen request on a settled decision. An answer from the user's message, recorded in the same command, supersedes the picks saved before it, and each decision's picksRead keeps a pick read again after a failed delete from changing anything. Turning off the wake deletes its link first, so open pages fall back to Copy answer, which stays as the fallback. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Inbox items in the coordinator's command center can now show pictures. On a Claude command center, the user can answer an item from the page instead of copying a prompt into the coordinator's thread.
Stacked on #185 (
feat/coordinator-command-center), the command center itself. This layer adds pictures and tap-to-answer to its Inbox.Summary
Pictures. A decision can carry
pictures, and each option can carry oneimage. Both are optional, so existing records still validate and text-only items look the same. Supported shapes:side-by-side(2–3)before-after(2)sequence(2–8, a numbered scroll strip)Pictures are committed under
files/and named by their content. The renderer stages them beside the page with the result thumbnails, and--checkfails when a named picture is missing or its bytes don't match its name. They are attached with the newrecord.py picturecommand or a report's askpictures. Tapping one opens it in an in-page viewer that pages through its group.Tap-to-answer. Each pick list gets Send answer beside Copy answer, but only when the page can read its database and a wake link:
sequenceDiagram participant Page as Command center (artifact) participant DB as Page database (owner-only) participant T3 as T3 webhook task participant C as Coordinator Page->>DB: set picks/<decision hex>-<revision> {decision, revision, option, label} Page->>T3: user taps "Wake the coordinator" (link read from config/wake) T3->>C: answer wake prompt (request carries nothing used) C->>DB: db_query picks, check owner and rules C->>C: record.py answer --stored <saved output> C->>DB: delete each listed pick at its version[{path: "", read: "owner", write: "owner"}], so only the artifact's owner, the user, can save or read picks.answer --storedtreats every document as untrusted. It records a pick only when its decision is open and the pick's revision and label match. The pick becomes the answer source.stalePick. An open decision asks again. A settled one becomes a runnable reopen request.picksReadnames every pick read for it by path and save time, so reading one again after a failed delete changes nothing.config/wakeon each Send, on each Wake tap, and when the user returns to it. Done, pause, a coordinator move or takeover, and leaving the artifact delete that document before the last read of stored picks, so an open page falls back to Copy answer.Skill. SKILL.md (heartbeat prompt, answer wake, Inbox and page, finish/pause/resume),
hosting.md(tap-to-answer setup, stored picks, turn off, untrusted input),program-state.md,decisions.md,coordinator-move.md,owner-kickoff.md, SOURCES, and README.Evidence
python3 scripts/check.pypasses on the head (coordinator suites: record, renderer, and 34 headless-Chrome page tests).--checkconfig/wakewhen it is removed or replacedasLeveladmin and interact) could neither read nor write.config/wake.db_queryoutput went throughanswer --stored, recording the current pick with its source and marking the stale one.record.py pictureand published them. A non-owner was refused again. Realdb_queryoutput carried each pick's version and save time,answer --storedrecorded the current pick, and a re-read changed nothing. The pick documents andconfig/wakewere deleted at their versions, and the webhook run succeeded.Merge Danger
This is a two-way door for code: reverting the PR restores #185's page and record. Records written with
pictures, optionimage,stalePick,picksRead, orgrant.wakewould then fail the older validator, so a program created on this layer needs those fields removed before running an older skill. Artifacts set up for tap-to-answer keep their owner-only database rule,config/wake, and webhook task until someone turns them off underhosting.md. A reverted page ignores them. It merges with the #182 ← #183 ← #185 stack and depends on #185's renderer and page.🤖 Generated with Claude Code