Skip to content

feat(control): the project screen asks its question with fewer things - #485

Merged
github-actions[bot] merged 1 commit into
mainfrom
feat/control-detail-density
Sep 4, 2026
Merged

feat(control): the project screen asks its question with fewer things#485
github-actions[bot] merged 1 commit into
mainfrom
feat/control-detail-density

Conversation

@catomean

@catomean catomean commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

Follow-on to #483. That gave the phone one pane per screen; this reduces what the remaining pane puts in front of you.

Measured on the live detail screen at 390px before touching it: 1088px tall, 114 words, 22 controls — and six different ways to start the same action: type + Send, tap "Suggested next", tap "Next best →", tap a history chip, open Prompt library, open "More". Six entry points to one job, with nothing saying which is normal.

Two changes, both removing duplication rather than hiding function

1. The "Send to agent" heading is gone. The composer directly above already asks the question — its placeholder is literally "What should the agent work on?" — so the kicker restated it, and worse put a section break between the two halves of one decision. Measured: the composer ended at y=779 and "Next best" began at y=924, reading as a separate feature rather than the other way to answer the same prompt. The honesty chip stays; it says something the button cannot ("Builder online").

2. One reuse affordance instead of two. RecentPromptChips and ProjectPromptLibrary do the same job with the same handleronPick={onCustomChange} and onSelect={onCustomChange}, both "put text in the composer" — yet rendered as two blocks with two headings: 4 of the 22 controls and ~150px, below the fold, competing with the composer they feed. They now share one labelled disclosure, closed by default.

CSS-only (max-lg:hidden plus a lg:hidden toggle), so there's no hydration branch and desktop is untouched — that card has the room and never had the problem.

Result

Same environment, same project, before → after:

before after
height 1088px 888px (−18%)
words 114 91 (−20%)
controls 22 19

Not done — named rather than implied

Of the 19 that remain, six are header context/navigation (streak, Focus terminal, Open here, branch, project details, agent setup) that you pass before reaching the question. That's the next lever.

And Autopilot on / Pause automatic continuation are two adjacent controls about whether it keeps going by itself. They are genuinely distinct (automationMode vs per-project auto-continue), so merging them is a semantics change I'm not making blind.

pnpm run verify passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P

Follow-on to #483. That gave the phone one PANE per screen; this reduces what
the remaining pane puts in front of you.

Measured on the live detail screen at 390px before touching it: 1088px tall,
114 words, 22 controls — and SIX different ways to start the same action (type
+ Send, tap Suggested next, tap Next best, tap a history chip, open Prompt
library, open More). Six entry points to one job, with nothing saying which is
the normal one.

Two changes, both removing duplication rather than hiding function:

1. THE "SEND TO AGENT" HEADING IS GONE. The composer directly above already
   asks the question — its placeholder is literally "What should the agent work
   on?" — so the kicker restated it, and worse put a section break between the
   two halves of ONE decision. Measured: the composer ended at y=779 and Next
   best began at y=924, reading as a separate feature rather than the other way
   to answer the same prompt. The honesty chip stays; it says something the
   button cannot ("Builder online").

2. ONE REUSE AFFORDANCE INSTEAD OF TWO. RecentPromptChips and
   ProjectPromptLibrary do the same job with the same handler —
   `onPick={onCustomChange}` and `onSelect={onCustomChange}`, both "put text in
   the composer" — yet rendered as two blocks with two headings, 4 of the 22
   controls and ~150px, below the fold, competing with the composer they feed.
   They now share one labelled disclosure, closed by default: a convenience
   does not get to open itself on the screen where space is scarcest.

   CSS-only (`max-lg:hidden` + a `lg:hidden` toggle), so there is no
   hydration branch and desktop is untouched — that card has the room and never
   had the problem.

Result, same environment, same project, before → after:

  1088px → 888px   (-18%)
  114 words → 91   (-20%)
  22 controls → 19

NOT DONE, and worth naming rather than implying otherwise. Of the 19 that
remain, six are header context/navigation (streak, Focus terminal, Open here,
branch, project details, agent setup) that you pass before reaching the
question — that is the next lever. And "Autopilot on" and "Pause automatic
continuation" are two adjacent controls about whether it keeps going by itself;
they are genuinely distinct (automationMode vs per-project auto-continue), so
merging them is a semantics change I am not making blind.

pnpm run verify passes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P
@github-actions
github-actions Bot merged commit c733f40 into main Sep 4, 2026
3 checks passed
@github-actions
github-actions Bot deleted the feat/control-detail-density branch September 4, 2026 13:44
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