Skip to content

Show Inbox pictures and let the user answer from the page - #186

Merged
sreejithraman merged 1 commit into
feat/coordinator-command-centerfrom
feat/inbox-pictures-tap-answer
Nov 15, 2026
Merged

sreejithraman merged 1 commit into
feat/coordinator-command-centerfrom
feat/inbox-pictures-tap-answer

Conversation

@sreejithraman

@sreejithraman sreejithraman commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

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 one image. Both are optional, so existing records still validate and text-only items look the same. Supported shapes:

  • one picture per option, beside its choice
  • 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 --check fails when a named picture is missing or its bytes don't match its name. They are attached with the new record.py picture command or a report's ask pictures. 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
Loading
  • The database rule is [{path: "", read: "owner", write: "owner"}], so only the artifact's owner, the user, can save or read picks.
  • answer --stored treats 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.
  • A pick for an earlier revision is never applied. It marks the decision's stalePick. An open decision asks again. A settled one becomes a runnable reopen request.
  • An answer from the user's message runs in the same command and supersedes picks saved before it. Each decision's picksRead names every pick read for it by path and save time, so reading one again after a failed delete changes nothing.
  • The import refuses output that is partial, paged, or missing documents, rather than skipping picks.
  • The page re-reads config/wake on 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.
  • Sites pages have no database and keep Copy answer alone.

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.py passes on the head (coordinator suites: record, renderer, and 34 headless-Chrome page tests).
  • New tests cover:
    • picture fields that validate, render, and stage, and a missing or misnamed picture failing --check
    • a stale revision that never applies
    • Copy answer after a stale pick
    • superseded picks, and picks read again after a failed delete
    • Send waiting for saved picks
    • Send and Wake following config/wake when it is removed or replaced
  • The last two browser tests and the consumed/superseded record tests fail with their fix removed.
  • End to end on a real private Claude artifact with the owner-only rule:
    • A non-owner (asLevel admin and interact) could neither read nor write.
    • The published page showed Send answer after reading config/wake.
    • A GET to the real T3 webhook returned 202 and woke the thread.
    • The stored db_query output went through answer --stored, recording the current pick with its source and marking the stale one.
    • A second run on the final commit attached option pictures with record.py picture and published them. A non-owner was refused again. Real db_query output carried each pick's version and save time, answer --stored recorded the current pick, and a re-read changed nothing. The pick documents and config/wake were deleted at their versions, and the webhook run succeeded.
    • The test artifacts and scheduled tasks were deleted afterward.
  • Not proven: tapping Send inside the Claude runtime, following the Wake link from the artifact frame on an iPhone, and a live heartbeat tick reading picks.
  • Screenshots at 390px (before, after, sent, before/after shape, stale note, viewer in light and dark) were reviewed locally.

Merge Danger

This is a two-way door for code: reverting the PR restores #185's page and record. Records written with pictures, option image, stalePick, picksRead, or grant.wake would 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 under hosting.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

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>
@sreejithraman
sreejithraman added this pull request to stack #184 November 15, 2026 23:09
@sreejithraman sreejithraman changed the title feat/inbox pictures tap answer Show Inbox pictures and let the user answer from the page Nov 15, 2026
@sreejithraman
sreejithraman merged commit 4370087 into main Nov 15, 2026
3 checks passed
@sreejithraman
sreejithraman deleted the feat/inbox-pictures-tap-answer branch November 15, 2026 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant