Skip to content

Tighten composer layout and visual hierarchy - #68

Merged
dovvnloading merged 1 commit into
mainfrom
codex/remove-starter-suggestions
Jul 29, 2026
Merged

Tighten composer layout and visual hierarchy#68
dovvnloading merged 1 commit into
mainfrom
codex/remove-starter-suggestions

Conversation

@dovvnloading

Copy link
Copy Markdown
Owner

Summary

  • Remove the redundant LOCAL ENGINE badge from the composer utility row.
  • Group model metadata, transient status, and character count into one compact right-aligned cluster.
  • Tighten the composer island width, padding, row heights, textarea spacing, and mobile dimensions.
  • Keep idle controls neutral and reserve the warm accent for an actionable send state.
  • Tone down model-menu icon/selection colors and reduce option density.
  • Add a regression test for the quieter utility row and update the UI audit.

Why

The composer is Cortex's primary control, but its previous utility row introduced too many labels, colors, and spacing changes at once. The result felt busy instead of deliberate. This pass gives the message field visual priority, makes secondary state information quiet, and makes the send action legible through availability rather than permanent color.

Validation

  • 45 frontend component tests (single-worker run)
  • 6 Playwright browser flows
  • Frontend typecheck, lint, and production build
  • Fresh Windows package build succeeded
  • Packaged launch returned GET /api/v1/health/ready with HTTP 200
  • Production bundle contains no removed LOCAL ENGINE badge
  • git diff --check clean

Scope note

The existing user-owned Cortex.pyproj worktree change was intentionally excluded. This PR is based on the already-merged UI and starter-removal changes from PRs #66 and #67.

@dovvnloading
dovvnloading marked this pull request as ready for review July 29, 2026 19:26
@dovvnloading
dovvnloading merged commit 69c3c3e into main Jul 29, 2026
1 check passed
@dovvnloading
dovvnloading deleted the codex/remove-starter-suggestions branch July 29, 2026 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant