Description
In the OpenCode desktop app, the message/output content area has a narrow max-width constraint that doesn't expand to use the full window width, even when the window is wide. This wastes significant screen real estate, especially on larger monitors.
Expected Behavior
The content area should either:
- Use the full available window width, or
- Provide a configurable
max_width setting (e.g. in tui.json or opencode.json) to let users control the content width
Current Behavior
Content is capped at a narrow width regardless of window size. Code blocks, diffs, and long lines get unnecessarily wrapped or truncated.
Suggestion
Add a config option like:
// tui.json or opencode.json
{
"max_width": 120 // or "full" to use available width
}Environment
- OpenCode desktop app (macOS)
Description
In the OpenCode desktop app, the message/output content area has a narrow max-width constraint that doesn't expand to use the full window width, even when the window is wide. This wastes significant screen real estate, especially on larger monitors.
Expected Behavior
The content area should either:
max_widthsetting (e.g. intui.jsonoropencode.json) to let users control the content widthCurrent Behavior
Content is capped at a narrow width regardless of window size. Code blocks, diffs, and long lines get unnecessarily wrapped or truncated.
Suggestion
Add a config option like:
Environment