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
Desktop/Web app: content area has narrow max-width, doesn't use full window width #16567
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)
Reacted by Hegyi Áron Ferenc, dayson and William E. H. Qvaale
This issue does not use one of the three required issue templates (Bug Report, Feature Request, or Question). Please resubmit using the appropriate template. If this is a feature request, the title should also start with [FEATURE]:.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
Activity
github-actions commentedon Mar 8, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Mar 8, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.
Feel free to open a new issue that follows our issue templates.