Overview
How might we let people arm search, code, image, and connectors before send without turning the composer into a settings panel?
When to use
- ChatGPT, Claude, Perplexity, and Gemini where search, image, code, or connectors change the next turn.
- Products with multiple capabilities that should be visible before send, not discovered after a failed answer.
- Bar chips when mode is the product (Perplexity Search vs Computer); + menus when most users should just type.
- Any composer where silent tool use would surprise people about cost, latency, or data leaving the thread.
When to skip
- Single-capability products where a tool picker is empty ceremony.
- Agent flows that must choose tools automatically and only need post-hoc disclosure.
- Mobile composers where a permanent row of mode chips crowds the send control.
States
Design the pre-send tool contract, not only the + menu icon.
- 01
Default
No tools armed. The composer reads as plain chat until the person opens the menu or taps a chip.
- 02
Browsing
The + menu or tool flyout is open. Search, attach, image, and connectors appear as peer choices.
- 03
Armed
One tool or mode is on for this turn. A single chip (or menu checkmark) shows what will run when they send.
- 04
Composing
Prompt text and the active tool coexist. Placeholder copy can shift to match the mode (search, image, think).
- 05
Sending
The message goes out with the selected tool. Tool choice travels with the prompt, not as a post-hoc guess.
- 06
Running
The model uses the armed tool. Status in the thread matches the chip that was visible pre-send.
Key UX elements
The parts that must be present for tool choice to feel intentional.
Menu
Group capabilities in one discoverable entry.
A + menu or tools button beats burying search, attach, and image in separate settings.
Chip
Show the one armed tool before send.
A single removable chip names the active mode. Switching tools replaces the chip instead of stacking more.
Toggle
Switch or turn off — don’t stack modes.
Pick another menu row to switch. Checkmark or second tap turns the current tool off. No pile of simultaneous mode chips.
Default
Pick a sane baseline per product.
Claude defaults web search on; Perplexity defaults Search. State the default in copy when it affects cost or latency.
Label
Use outcome language, not infra names.
Search, Create image, and Thinking beat internal tool IDs. Note when a mode is slower or uses credits.
Conflict
Treat modes as exclusive when they collide.
Search, Think, and Image should replace each other. Don’t let incompatible modes run in parallel.
Rules
Hidden tools with no discoverable entry until after the user fails.
Stacking multiple exclusive modes as simultaneous chips (Search + Think + Image all on).
Active tools with no removable chip, checkmark, or clear off state.
Mode labels that change cost or latency without saying so.
Evidence
| Product | Implementation |
|---|---|
| ChatGPT | + menu for attach and modes; picking Search, Think, or Image replaces the prior mode with one chip. |
| Claude | Web search toggles with a checkmark in the + menu; skills and attach share the same entry point. |
| Perplexity | Primary mode chips (Search, Computer) are exclusive; + covers uploads and connectors. |
| Gemini | + menu leads with Drive; Deep research and creation tools in flyouts. |
