Skip to content

[Bug] Session timeline is narrower than the composer after v2026.5.5 #455

@Astro-Han

Description

@Astro-Han

What happened?

After upgrading to v2026.5.5, the session timeline/content column appears narrower than the composer/input bar. The visible result is that the conversation flow no longer lines up with the input area, making the session layout feel inconsistent.

This report is about the layout width relationship between the session flow and the composer. Any typography-token or #440 design-token change should be treated as investigation context only, not as the reported user-facing symptom.

Which area seems affected?

UI or design system

How much does this affect you?

Makes a workflow harder, but there is a workaround

Steps to reproduce

  1. Install or open PawWork v2026.5.5.
  2. Open a normal session with existing messages.
  3. Compare the visible session timeline/content column with the composer/input bar at the bottom.
  4. Notice that the session flow appears narrower than the input bar.

What did you expect to happen?

The session timeline and composer should share a coherent width contract. The conversation flow should not appear narrower than the input area unless that is an explicit, intentional design decision.

PawWork version

v2026.5.5

OS version

macOS, exact version not captured in the initial report.

Can you reproduce it again?

Yes, every time

Diagnostics

Observed screenshot: the session content column appears visually narrower than the bottom composer/input bar.

Initial local checks found that the packaged app still contains the expected responsive width classes, so this may not be a simple missing-CSS packaging issue.

Observed width-related code paths to inspect:

  • Session timeline/content width is controlled in packages/app/src/pages/session/message-timeline.tsx.
  • Composer width is controlled in packages/app/src/pages/session/composer/session-composer-region.tsx.
  • Existing E2E coverage for composer width appears to measure the outer full-width dock layer rather than the visible composer surface, so the regression may need a more precise layout test.

Possible related context to verify before fixing:

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Medium prioritybugSomething isn't workinguiDesign system and user interface

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions