Problem
On wide screens (e.g., external monitors, ultrawide displays), the chat content area is constrained to a fixed narrow column (~720px max-w-content), leaving large amounts of unused whitespace on both sides. This wastes screen space and doesn't look great.
Current Behavior
- The left sidebar takes ~200px
- The chat content area is capped at ~720px width regardless of screen size
- On a 1440p+ display, more than half the right side is empty whitespace
Expected Behavior
The chat content area should scale responsively with the available viewport width:
- On normal screens (< ~1200px): current behavior is fine
- On wide screens (> ~1200px): the content area should expand to use more horizontal space
- Consider a wider max-width breakpoint (e.g.,
max-w-4xl or max-w-5xl at xl: / 2xl: breakpoints)
- Or use a percentage-based max-width (e.g.,
max-w-[85%]) so it always fills most of the available space
Screenshots

The chat content area only uses a small portion of the available space on the right side.
Possible Implementation
The max-w-content (720px) is likely defined in web/tailwind.config.ts and used in components like HappyComposer.tsx and the thread/message area. A responsive approach could:
- Increase
max-w-content at larger breakpoints
- Or use
xl:max-w-4xl 2xl:max-w-5xl overrides on the content container
Problem
On wide screens (e.g., external monitors, ultrawide displays), the chat content area is constrained to a fixed narrow column (~720px
max-w-content), leaving large amounts of unused whitespace on both sides. This wastes screen space and doesn't look great.Current Behavior
Expected Behavior
The chat content area should scale responsively with the available viewport width:
max-w-4xlormax-w-5xlatxl:/2xl:breakpoints)max-w-[85%]) so it always fills most of the available spaceScreenshots
The chat content area only uses a small portion of the available space on the right side.
Possible Implementation
The
max-w-content(720px) is likely defined inweb/tailwind.config.tsand used in components likeHappyComposer.tsxand the thread/message area. A responsive approach could:max-w-contentat larger breakpointsxl:max-w-4xl 2xl:max-w-5xloverrides on the content container