Repository navigation
Description
Type: Feature request / discussion
Summary
On wide / fullscreen terminals, the session message area doesn't make good use of the available width. The effective content reads as a narrow band with large empty margins on the sides, so a lot of screen real estate is wasted.
What I found in the source
While looking at packages/tui/src/routes/session/index.tsx:
layout("auto" | "stretch") in the main config is@deprecatedand now always usesstretch(seehttps://opencode.ai/config.json), so the column should already stretch to full width.- The sidebar auto-shows when
dimensions().width > 120and consumes 42 columns (index.tsx:265,index.tsx:273):const wide = createMemo(() => dimensions().width > 120) const contentWidth = createMemo(() => dimensions().width - (sidebarVisible() ? 42 : 0) - 4)
- The message container is
flexGrow={1}withpaddingLeft/Right={2}(index.tsx:1168-1169), and individual messages have nomaxWidth— they fill the available column.
So on a wide terminal the main levers left are the hardcoded 120 sidebar threshold and the 42-col sidebar width. Hiding the sidebar (session.sidebar.toggle) reclaims width, but the threshold itself isn't configurable, and on ultra-wide terminals full-width raw text is hard to read, so some users actually want an opt-in centered column.
Proposals (open for discussion)
- Make the
widethreshold (120) configurable via the TUI config (e.g.session.sidebar_width/session.wide_threshold), so users on smaller-but-wide terminals can keep messages wide. - Add an optional
session.content_max_width(similar to the existingprompt.max_widthon Home,config/index.tsx:48) so ultra-wide users can center a readable column, while narrow users keep full stretch. - Auto-hide the sidebar when showing it would push
contentWidthbelow a minimum ratio.
Environment
- opencode: latest
dev(cloned for source reading) - Terminal: wide/fullscreen (please confirm your exact width + whether sidebar is visible when you see this)
Willing to contribute
Happy to open a PR once a direction is agreed. The change for proposal 1 is small (a couple of lines); proposal 2 is a bit more involved but still contained to routes/session.
Activity
github-actions commentedon Jun 19, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:(e.g.[FEATURE]: Better use of horizontal space in the session view on wide terminals)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:
tui.jsonoption to control content area max-width / horizontal padding on wide terminalspaddingLeft/Rightvalues)If you believe this was flagged incorrectly, please let a maintainer know.
7nicetoseeu commentedon Jun 19, 2026
Closing this as a duplicate — apologies, I should have searched before opening.
After the bot pointed them out, I see the same asks are already tracked (and two are assigned to @kitlangton):
My proposal 1 maps to #6087, proposal 2 maps to #25142, and the padding concern to #20230. Rather than fragment the discussion, I'll move over to #25142 and share the source-level findings there, and I'm happy to help with a PR on any of these.
7nicetoseeu commentedon Jun 19, 2026
Closing as duplicate of #25142, #6087, and #20230. See comment above.