Regression: non-file feed operations collapse to opaque Ran ellipsis rows #530

Activity

1. Juliusolsson05 commented on Aug 26, 2026

   

   Juliusolsson05

   on Aug 26, 2026

   OwnerAuthor

   More actions

   Additional retained-session evidence from 2026-08-26 shows a related presentation failure after the original opaque-ellipsis regression:

   A committed Codex unified exec wrapper was safely normalized to its inner tools.exec_command. The inner command consisted entirely of rg, rg --files, sort, and head, but the durable row still presented the transport-level label exec, raw shell text, and exit unknown.

   The route is structurally correct (codex.rows.dispatch owns the invocation and paired output), so the Unknown Shape Inbox considers it known-claimed. The remaining failure is semantic presentation: the shared command protocol has no conservative search/read/list operation model.

   Proposed additional acceptance criteria:

   • Fully parsed, read-only discovery commands render as Search, Read, or List operations while preserving exact command/output disclosures.
   • Classification is parse-full-or-decline. Mixed or mutating expressions such as rg foo && rm file, redirection, find -delete, and sed -i remain ordinary commands.
   • Transparent wrappers that discard the inner exit code say that the exit code is unavailable; they never imply success or show the ambiguous phrase exit unknown.
   • The specialized receipt includes a stable protocol identifier so known-claimed generic command presentation can be audited separately from semantic discovery presentation.
2. Juliusolsson05 commented on Sep 20, 2026

   

   Juliusolsson05

   on Sep 20, 2026

   OwnerAuthor

   More actions

   Obsolete — every file this issue names was deleted by the #555 renderer rewrite, and the contract it asked for is met by what replaced them.

   Gone: features/feed/ui/resolve/fromLive.ts, ui/artifacts/command.tsx, ui/operations/OperationRow.tsx, presentation/projectBlock.ts; commandFromLive, CommandCard and the command: '…' fallback have no occurrences anywhere.

   What replaced them does the right thing by construction. src/providers/shared/renderer/protocols/command/model.ts states the rule in its header — streaming-first: a model must be paintable the moment the command string is known, with output and exit arriving as props updates to the same row — and src/providers/claude/renderer/adapters/command.ts:30-52 emits the real command text with status: 'streaming'. Critically, fromClaudePartialBashJson (:55-64) returns null until the command JSON field closes, so a half-streamed command is never painted as a headline; and Codex's adapter declines with return null rather than inventing a placeholder. That is the opposite of the opaque "Ran …" collapse this issue reported.

   One acceptance item does survive, recorded here rather than lost: a declined Codex partial falls through to the generic/fallback route, not to an explicitly-named "preparing"/"running" row. If that named intermediate state still matters, it wants a fresh issue against the current protocol model — this one points at code that no longer exists.
3. Juliusolsson05

   closed this as completedon Sep 20, 2026