[FEATURE]: Resizable session content width in Desktop/Web #53382

Activity

1. github-actions

   assigned

   Brendonovich

   on Oct 5, 2026
2. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   and removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Oct 5, 2026
3. github-actions commented on Oct 6, 2026

   

   github-actionsBot

   on Oct 6, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for updating the issue with the verification checkbox and a clear description of the requested change.
4. hril3 commented on Oct 19, 2026

   

   hril3

   on Oct 19, 2026

   More actions

   Since #56953 got flagged as a duplicate of this, here's the root-cause trace from the current dev source (ba06ff9e0b), plus the two gaps the triage bot called out.

   How the clamp works

   The width is not a user preference anywhere — it is derived from a media query:

   // packages/app/src/session/model.ts:29
   const isDesktop = createMediaQuery("(min-width: 768px)")

   // packages/app/src/session/screen-layout.ts:106
   centered: createMemo(() => session.isDesktop()),

   So any viewport wider than 768px gets centered = true, and that switches on a Tailwind utility that resolves to a design-token constant:

   // packages/app/src/session/timeline/message-timeline.tsx:406
   "md:max-w-session md:mx-auto": props.centered,

   /* packages/ui/src/styles/tailwind/index.css:53 */
   --container-session: 744px;

   Worth noting for scoping: this is not desktop-specific. Since isDesktop is (min-width: 768px), the web UI is clamped identically as soon as the window passes 768px. There is no code path a user or config can influence.

   All consumers of the constant

   Seven places consume max-w-session, so a single override point has to cover all of them (line numbers as of ba06ff9e0b):

   File	Line	Consumer
   packages/app/src/session/timeline/message-timeline.tsx	406	message column
   packages/app/src/session/composer/session-composer-region.tsx	34	composer
   packages/app/src/session/route.tsx	71	session page container
   packages/app/src/session/preparing-composer.tsx	50	loading-state composer
   packages/app/src/composer/dropzone.tsx	55	drag overlay
   packages/session-ui/src/timeline/session-timeline-row.tsx	480	row wrapper (session-ui package)
   packages/app/src/new-session/layout.ts	2	new-session page (separate hardcoded 880px)

   That last row is the second gap worth flagging: the new-session page has its own hardcoded max-w-[880px] in NEW_SESSION_CONTENT_WIDTH rather than using the token, so it needs a separate change even after the session column is resizable.

   On the two points the triage bot raised

   1. Settings affordance — surfacing the current width plus a "reset to default" control seems worth doing, since otherwise the value is only reachable by dragging (double-click to reset works, but it is undiscoverable).
   2. The 880px new-session page — as above, separate constant, same limitation.

   I don't want to duplicate the scope described here; happy to follow whatever direction you maintainers prefer. If you open a PR for the session column, I can contribute the parts above (or just review them).
5. dchasman commented on Oct 24, 2026

   

   dchasman

   on Oct 24, 2026

   More actions

   The fixed-width message column remains a usability problem on wide desktop windows. Please keep one canonical issue open until configurable width is implemented or explicitly declined.

   Earlier reports were closed for administrative reasons, not because the limitation was resolved:

   Issue	Closure reason	Evidence
   #29408 — Desktop wide mode	Automatically closed after 60 days without activity	github-actions: “To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.”
   #16567 — Narrow Desktop/Web content area	Automatically closed for template noncompliance after a 2-hour deadline	github-actions: “This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.”
   #14834 — Fixed-width chat wastes screen space	Automatically closed for template noncompliance after a 2-hour deadline	github-actions: “This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.”
   #56953 — Session content locked to 744px	Closed as a duplicate of #53382, not as fixed	opencode-agent: “Closing as a duplicate of #53382, as agreed. That issue covers the same request: a resizable session column with a saved width and a reset.”

   Not all of these closures were due to inactivity, but none demonstrates that the underlying request was delivered.

   Requiring users to recreate unresolved requests fragments the discussion, loses continuity, and makes the actual implementation status difficult to follow. Lack of comment activity does not mean the limitation has disappeared.

   Please exempt this canonical issue from inactivity-based closure, or provide a durable tracking item that will remain open until the request is implemented or explicitly declined.
6. Wiedzmin-git commented on Oct 27, 2026

   

   Wiedzmin-git

   on Oct 27, 2026

   Author

   More actions

   Thanks for the discussion. I’m stepping away from the project and won’t be preparing a PR for this proposal. Since other users are interested, I’m leaving the issue open for others to take forward.
7. opencodejr commented on Oct 27, 2026

   

   opencodejrBot

   on Oct 27, 2026

   Contributor

   More actions

   Thanks for the careful write-up and for linking the earlier requests.

   To restate it: you'd like to be able to resize the session column in Desktop/Web by dragging either edge, so the timeline and composer change width together. The width would be saved and kept within the available space, with the current responsive default until you change it, an easy reset, keyboard resizing and RTL support. Right now the column width is a fixed design value (--container-session, 744px on most desktop widths), so this would be a new option rather than a bug fix. The maintainers will consider it, and since you offered a PR, they can tell you whether this design works for them before you adapt it to the current branch.

   Related issues:

   • desktop: session column capped at 744px on wide monitors, clipping diagrams and tables #54800: same problem (column capped at 744px on wide monitors, clipping diagrams and tables), asking for fill-width or a drag handle
   • app: session content locked to 744px on wide windows - no way to use the remaining width #56953: closed as a duplicate of this issue; the root-cause trace and the Settings / new-session 880px notes were moved here
   • [FEATURE]: Add desktop wide mode to use full available chat width #29408, Chat content width is fixed at 800px, wasting screen space on wide monitors #14834, Desktop/Web app: content area has narrow max-width, doesn't use full window width #16567, Chat window size is too narrow in desktop app #29430, Desktop UI should prioritize desktop workflows and screen real estate #15735: earlier wide-mode requests, now closed; feat(app): add wide mode setting to use full window width for chat #14835 was an earlier wide-mode PR that wasn't merged
   • [FEATURE]: Add tui.json option to control content area max-width / horizontal padding #25142: the same idea for the TUI (content max-width / padding)
8. VetiSantiagoO commented on Nov 10, 2026

   

   VetiSantiagoO

   on Nov 10, 2026

   More actions

   +1 to this. The fixed 744px column is the main thing that keeps me from using the desktop app on a wide monitor. Code blocks, diffs, tables and Mermaid diagrams wrap or scroll sideways while half the window sits empty.

   I'd like to suggest a simpler first step that could ship before (or instead of) drag-to-resize: a content width preset in Settings → Appearance:

   • Narrow: the current 744px, kept as the default so nothing changes for existing users
   • Medium: around 1000px, the cap before v2.0.27 (desktop: session column capped at 744px on wide monitors, clipping diagrams and tables #54800)
   • Wide: fills the available width, minus the normal padding and any open side panel

   Why presets might be easier to land:

   • They map onto the existing --container-session variable, so the change mostly means swapping a hardcoded value for a setting-driven one. That should also cover the hardcoded 880px on the new-session page mentioned above.
   • There's no new drag handle to reconcile with the review/side panel splitter, its min-widths, or the layout transitions.
   • The setting persists like any other appearance preference and is easy to reset.
   • A command palette entry (e.g. "Cycle content width") would make it quick to switch, for example going wide when reviewing a large diff and back to narrow when reading prose.

   Drag-to-resize could still come later on top of this, as a "Custom" option.

   👍React with 👍1Reacted by Doug Chasman
9. LorenzoServolini commented on Nov 11, 2026

   

   LorenzoServolini

   on Nov 11, 2026

   More actions

   Until a resizable width lands, I published a small plugin that makes the built-in Wide option fill the whole window (OpenCode Desktop 2.x): opencode plugin add opencode-wide-chat → https://github.com/LorenzoServolini/opencode-wide-chat

   🚀React with 🚀1Reacted by Doug Chasman
10. dchasman commented on Nov 13, 2026

    

    dchasman

    on Nov 13, 2026

    More actions

    Until a resizable width lands, I published a small plugin that makes the built-in Wide option fill the whole window (OpenCode Desktop 2.x): opencode plugin add opencode-wide-chat → https://github.com/LorenzoServolini/opencode-wide-chat

    Your plugin is fantastic! Thank you so much for building it! @LorenzoServolini

    ❤️React with ❤️1Reacted by Lorenzo Servolini