4.4 KiB
4.4 KiB
Phone-size feedback (operator, 2026-10-23)
Status: [ ] open, [x] landed (with commit).
Overall
- O1 Search moves from the action bar to a 5th bottom tab.
Runs page
- R1 "Usage: {...}" leaves the list; a chart icon in the action bar opens a stats page (pie chart and other charts).
- R2 Filter and Sort become action-bar icons; the filter text field moves into the filter popup.
- R3 Run list item laid out by meaning (pipeline name, run, start/end, duration, stages run, status) instead of concatenated text.
Run detail
- D1 Pipeline-related actions (Rename, Schedule this run) move to a "more" icon in the action bar.
- D2 Tabs: Summary+Graph, Timeline, Artifacts, Changes. The graph sits on top of Summary as a non-interactive preview; tapping opens it full screen with interaction.
- D3 (superseded) Retry sits next to the failed status, only when failed.
- D4 The tabs are bottom tabs on mobile.
- D5 Summary facts use less space (several facts per line).
- D6 Drop "Original prompt"; keep Input and Output, showing the actual data rather than raw JSON.
- D7 (
d924da2b) Graph drawing: a linear pipeline row with the success/failure ends below it (see the TUI and web renderers). - D8 Timeline: real status icons (not empty circles) and well-laid-out items.
- D9 A diff opens as its own page with previous/next file in the change set.
- D10 Artifacts and Changes: previous/next as chevron icons bottom-right, in one row.
Pipelines page
- P1 List item: information placed in the corners, not concatenated.
Chat
- C1 Send is a send icon (
74fe1254). - C2 No "Assistant is responding" line (
74fe1254). - C3 (order 7e93348b; bubbles c2f1a4cb; reasoning/tool chip
eaa4f24e) Messages render in order: each reply after the message it answers, one reply box per reply (web parity for tool calls and message layout).
Desktop layout: later.
Follow-ups noticed while working:
- Cupertino tool sheet: a screen-reader activation of a call row did not expand it in the browser probe (a pointer tap does); check the disclosure's semantics inside the popup route.
- Browser probes title_wiring_probe.mjs and retry_wiring_probe.mjs still look for Rename in the header; it now lives in the more menu (D1).
Later requests (2026-10-23):
- Chat: reasoning is a chip beside the tool chip, opening its own sheet
(
27203fb7). - Run detail: the pipeline name links to that pipeline at the run's
version; Retry is a more-menu option for failed runs, replacing D3
(
f3bd91ba).
Changes, stages and artifacts (2026-10-23, later):
- X1 Remove the "Filter changed files" input.
- X2 The Changes tab shows the run's final changes (the end state).
- X3 Per-stage changes show in each stage's detail opened from the timeline.
- X4 A stage clicked in a pipeline opens its own page, not an inline pane.
- X5 Artifacts show a small preview beside each item, especially images.
- An open run takes over the app bar: Back, "Run N", the more menu; the in-page Back row is gone inside the shell (shell bar registry, lib/shell/shell_bar.dart). Tabs remember their last screen.
- Search probe (tool/search_probe*.mjs) still clicks the old bar action.
More (2026-10-23, evening):
- Y1 Run summary: Diagnostic in a collapsible.
- Y2 Stage page: Input/Output/Changes/Session/... as bottom tabs; Input and Output as values, not JSON; one Back (the bar's); no "Back to timeline".
- Y3 Artifacts: one gallery look for run and stage: a grid with thumbnails where possible, a file-type icon otherwise.
- Y4 More colour: diff +N green, -N red.
- Y5 Runs list: the attention bell moves to the app bar.
- Y6 Pipelines page: refresh, filter and sort move to the app bar.
- Y7 Chat: a pasted image shows a thumbnail in the composer.
- Z1 Run and stage bottom tabs show an icon above each name.
- Z2 Pipeline detail: Run and Runs become action/FAB buttons.
- Z3 Chat list: no search; refresh and New chat in the app bar.
- Z4 Chat rows: the agent kind (opencode/claude/...), the model, and ~ for the home directory.
- Z5 Inside a chat: show the current model (the model dropdown has no label of what is chosen).
- Z6 Run graph: colour the stage status so it reads apart from the name; number the visited edges in visit order (1, 2, 3...).