[Play review] Selectable-options dropdown shows an incomplete .json when the previous request came from another device #248

Activity

1. dzianisv commented on Nov 14, 2026

   

   dzianisv

   on Nov 14, 2026

   OwnerAuthor

   More actions

   DevRel verification (2026-11-15, main 01a7b6b): not verified as worded — no code path renders JSON into the options dropdown.

   What I checked:

   • The selectable-options UI (QuestionPrompt, rendered from app/session/[id].tsx) renders option labels verbatim. The v2 mapping (src/lib/v2-shape.ts toQuestionRequest) builds options as { label, description } with no JSON construction, truncation, or parsing anywhere in the path; v1 passes the server payload through as-is. A JSON fragment as an option label could only come from the server sending a JSON string as the label/value — no evidence of that in this repo.
   • One adjacent, code-verified rendering of truncated JSON exists on a different surface, and it fits the cross-device condition: a question answered from another device never shows the live QuestionPrompt on this phone, so its only trace is the history tool-call card. ToolCallCard has no 'question' case, so it falls through to GenericDetail (src/components/chat/ToolCallCard.tsx), which renders the raw tool input as JSON.stringify truncated at 30 lines. That card shows no selectable options and is collapsed by default, so it does not match 'question card shows selectable options' — but it is the leading hypothesis for what the reviewer saw.

   Closing as unverified (2026-11-15). What would reopen it: a screenshot showing exactly which card displayed the JSON (options list vs. an expanded history tool-call card), and the form payload for that session.
2. dzianisv

   closed this as not plannedon Nov 14, 2026