Skip to content

fix(opencode): show bash commands instead of repeating their output - #7989

Open
brynne8 wants to merge 2 commits into
pingdotgg:mainfrom
brynne8:fix/opencode-bash-command-preview
Open

fix(opencode): show bash commands instead of repeating their output#7989
brynne8 wants to merge 2 commits into
pingdotgg:mainfrom
brynne8:fix/opencode-bash-command-preview

fix(opencode): keep failure reason on failed bash tool rows

e343705
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - UI Consistency succeeded Aug 23, 2026 in 27s

UI Consistency: No findings

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/ui-consistency.md
More information about how Check Run Agents work can be found in our Help Center.

In-scope changes are limited to apps/web/src/session-logic.command-output.test.ts, which adds a unit test for OpenCode bash command/rawOutput derivation. No web components, primitives, Tailwind classes, global CSS, theme variants, or scroll/virtualization behavior were modified. Verified that no web module reads the removed payload.data.state field from the OpenCode adapter projection, so the server-side shape change does not create a client rendering regression.


🔍 Agent activity — 3 tool calls

💭 The diff only touches a server adapter and a web test file, and since the test file falls in scope but involves no UI changes, this looks like a case where there's nothing to flag for UI consistency. I'm noting a tension though — the instructions ask for a plain "All clear" response, but the output format also needs to follow a JSON schema, so I need to reconcile that. Given no UI component changes here, I'll produce a success result with a summary indicating all clear. Let me just double-check that the test's expectations line up with the actual session-logic behavior before finalizing, just to be thorough.

1. git_tools — rawOutput

2. browse_code — apps/web/src/session-logic.command-output.test.ts

💭 No UI styling changes here, but I'm wondering if removing state: part.state from the server data could affect the web UI's rendering of opencode tool parts, since the frontend might rely on that field. Let me check whether the session logic code actually reads data.state.

3. git_tools — data?.state|data.state|"state"

💭 I confirm there's no web consumer of payload.data.state, so this looks safe.


Agent Credits: 24 credits