You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
tui: input area covered by black rectangle during heavy tool-call/reasoning on v2 #38773
In TUI mode on the v2 branch, the input field (and slightly above it) is
intermittently covered by a solid black rectangle, blocking text entry. The
issue occurs consistently when the model performs many tool calls or extended
reasoning. The only workaround is re-entering the session.
Expected Behavior
The input area should remain visible and usable at all times, regardless of
model activity.
Actual Behavior
A black rectangle occludes the input field and a small region above it after
the model initiates several tool calls or extensive reasoning. The rest of
the chat history remains visible. Re-entering the session (connecting again)
clears the artifact.
Additional Context
Frequency: Consistent – reproduces every session when the model does
many tool calls or long reasoning chains.
First noticed: On the v2 branch only (the opencode2 binary); did not
occur on v1.
Workarounds tried: Re-entering the session (only known workaround).
Resizing the terminal window and pressing Escape do not help.
Logs:~/.local/share/opencode/log/opencode.log shows no errors or
warnings related to rendering – only standard INFO-level startup and
keepalive messages.
Terminal: Ghostty with OpenGL renderer. Other terminal features
(ligatures, truecolor, etc.) work correctly.
Open opencode in TUI mode (run opencode without subcommands).
Start a session with a model that uses tool calls or spends significant
time reasoning (e.g. multiple sequential tool calls).
While the model is producing tool calls or reasoning output, observe the
input area at the bottom of the terminal.
At some point the input field (and a couple of lines above it) becomes
covered by a solid black rectangle, making it impossible to type or see
the prompt.
Could you temporarily disable your Ghostty custom-shader (cursor_smear.glsl) and check whether this still reproduces? Cursor shaders render after the terminal surface and may overlay the TUI during frequent cursor updates.
Could you temporarily disable your Ghostty custom-shader (cursor_smear.glsl) and check whether this still reproduces? Cursor shaders render after the terminal surface and may overlay the TUI during frequent cursor updates.
Activity
opencode-agent commentedon Jul 25, 2026
Could you temporarily disable your Ghostty
custom-shader(cursor_smear.glsl) and check whether this still reproduces? Cursor shaders render after the terminal surface and may overlay the TUI during frequent cursor updates.ReStranger commentedon Jul 26, 2026
ReStranger commentedon Jul 31, 2026
The problem went away with the update :D