Skip to content

[Feature Request]: Add adjustable conversation pane width (percentage) in Desktop GUI #151

Closed

Description

@lidao2026-Coding

Is your feature request related to a problem?

Yes. The Desktop GUI conversation pane has a fixed width that is too narrow — on wide Windows monitors (1440p/4K) the chat column occupies only a small portion of the screen center while both sides are large empty spaces. This wastes screen real estate and makes long conversations harder to read.

Describe the solution you'd like

Add a conversation pane width setting (in percentage), e.g. 40%–90%, adjustable in Settings, and/or a drag-to-resize handle between the conversation pane and the side panels. The choice should persist across sessions.

  • Settings → Appearance: "Conversation pane width: 60% (slider)"
  • Optional: a draggable splitter for quick manual adjustment, with the percentage synced back to settings

Describe alternatives you've considered

  • Auto-expand the chat pane to fill the window when side panels are collapsed.
  • A fixed "wide mode" toggle.

Additional context

  • Platform: Windows 11, 2560×1440 display.
  • Version: DeepCode Desktop 0.1.0 (v2.0.0 runtime).
  • This is purely a UI/layout improvement; no backend changes needed (frontend: desktop/src/**).

Activity

  1. Zongwei9888 commented on Aug 6, 2026

    @Zongwei9888
    Collaborator

    Thanks — implemented in #161. Settings → Appearance → Conversation width, adjustable from 40% to 100%.

    Your diagnosis was right: the column was pinned to a fixed maximum. It turned out the same constant was hardcoded in three separate places (the conversation, the composer and the goal rail), so they all share one value now. At 100% the original width is restored, so nothing changes unless you move the slider.

    The drag-to-resize handle you mentioned as an alternative isn't built yet — the slider seemed like the smaller step and should cover the main problem. If the handle would help in daily use, let us know and we'll look at adding it.

  2. added 2 commits that reference this issue on Sep 22, 2026
  3. Zongwei9888 commented on Sep 28, 2026

    @Zongwei9888
    Collaborator

    Closing this as complete — both halves of the request are now in main. Thank you @lidao2026-Coding for the clear write-up; the diagnosis (one fixed width hard-coded in several places) was exactly right.

    If anything about the behaviour on your 1440p/4K setup still feels off, please open a new issue with a screenshot and we will take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions