Repository navigation
[UI-01] Add Standard, Wide and Full width chat layouts #23
Description
Requested only; no implementation. Baseline:
bc9eeb9a6f5e3fe2e6d58d9c1b14d5ed93d6c2be (0.0.42-preview.20261003.2).
Backlog: #1.
Tpatch: chat-content-width.
Branch: request/chat-content-width.
Versioned request.
Problem
On large monitors, the conversation and composer stop widening at max-w-3xl
(48rem, about 768 CSS px at the default interface size), leaving large margins.
Smaller panes fill and wrap normally. There is no current width setting;
increasing interface font size changes rem geometry but also enlarges the UI.
Proposed outcome and acceptance
- Client-local Appearance preference: Standard / Wide / Full width.
Keep current 48rem Standard behavior and default. Choose the Wide maximum
during responsive evaluation; font size is not a substitute for this control. - Use available chat-pane width with safe gutters, not full window width behind
sidebars/right panels. Keep composer, messages and related panels aligned. - Audit nested max-width wrappers, status/work rows, approvals/questions/plans,
code/tables/images, virtualized measurements and scroll anchoring. - Cover drafts and existing threads, first-project state, narrow/wide windows,
split panes, browser zoom, large fonts and both theme appearances. - Persist per device/browser; Settings search and reset; older-settings
compatibility. No provider or server execution-state change. - Web/desktop share layout. Explicitly decide native tablet/mobile coverage
rather than stretching phone layouts or assuming React Native inherits CSS. - No continuously animated resizing or per-row polling.
Source:
timeline maximum,
composer maximum,
font/rem behavior.
Independent of #18's narrow-window send shortcuts, #22's Windows menu/dragging
issue, and proposed channel artwork or active-environment identification.
No runtime implementation, phase advancement, browser automation, build/CI,
live-state changes, PR or release in this request registration.
Recorded by GPT-6 Astra using GitHub Copilot CLI; no delegated inference.
Activity
jdbencardinop commentedon Oct 3, 2026
Request registration published at
fd784c6e74913b321ea934778284cf25a184301bonrequest/chat-content-width. It contains only request/status metadata and the generated tpatch dashboard; product bytes equal baselinebc9eeb9a6. Lifecycle remains requested. Independent Windows menu/title-bar proposal: #22.jdbencardinop commentedon Oct 29, 2026
Upstream coverage candidate confirmed in stable v0.1.3: Comfortable (48rem, default), Wide (72rem), and Full chat widths, including composer alignment, Settings search/reset and desktop reuse. Introduced by pingdotgg#11594. Do not implement a duplicate width root before reconciliation; validate the exact requested behavior on the fork and retire/satisfy only after its visual and reviewer gates pass. Native mobile was intentionally unchanged by upstream. Issue remains open.
jdbencardinop commentedon Oct 29, 2026
Upstream v0.1.3 supplies Comfortable / Wide / Full in Settings → Appearance. In the isolated web client at 1800px, an existing thread's focused composer measured 710px → 1126px → 710px when switching Comfortable → Wide → Comfortable. The preference was restored afterward.
The reviewer inspected the settled layout captures. Full is exposed in the UI but was not separately measured; native Electron/receiving-host qualification is separate. No duplicate width patch was added.
Comfortable
Wide
jdbencardinop commentedon Oct 29, 2026
Retested upstream width controls on v0.1.4: existing-thread editor measured 710px → 1126px → 710px using Settings → Appearance → Chat width. Captures include the reverse transition. No duplicate custom width feature was added.
Reviewed report and visual evidence: #1 (comment)
Candidate only; no main promotion or live upgrade.