What it means
The composer aggregates text input, attachments, mode toggles (Search, Agent, Build), connector chips, and send/stop into the main interaction control of the product.
Why designers should care
Composer density is a core design problem: too empty and users face prompt anxiety; too crowded and power features hide. Progressive disclosure and mode clarity matter.
Example
Manus frames the composer with connector suggestion cards, + attach menu, skills via slash commands, and Lite/Pro/Max tier picker before the agent runs.
Common mistakes
- Blank textarea with no starters, modes, or capability hints.
- Cramming every feature into one row with no grouping or overflow menu.
- Send and Stop using the same visual weight, causing accidental interrupts.
Frequently asked questions
What is Composer?
The composer is the primary input surface where users assign tasks to AI: type prompts, attach files, pick modes, arm connectors, and send.
Why should designers care about Composer?
Composer density is a core design problem: too empty and users face prompt anxiety; too crowded and power features hide. Progressive disclosure and mode clarity matter.
What are common mistakes with Composer?
Blank textarea with no starters, modes, or capability hints; Cramming every feature into one row with no grouping or overflow menu; Send and Stop using the same visual weight, causing accidental interrupts.