# AI Suggestion (Intent Screen) > A short screen shown before an agent session opens. - Area: Desktop app - Plans: All plans - Last checked against the product: 2026-09-28 - Web page: https://agentsroom.dev/docs/ai-suggestion-intent-screen ## What it does A short screen shown before an agent session opens. You describe in one sentence what the agent is about to do, and a single call returns the cheapest model in the provider's catalogue that can still do the job, a generated session name and, when no agent was chosen, the agent itself (among the agents already in the room, the 14 built-in roles and, on Pro, the whole expert catalogue). The session then opens already configured, with your description delivered as its first message. The point is economic: most people open every agent on the most capable model; a typo does not need a flagship. ## Where to find it - On an agent card without a live session: the accent sparkle button in its action bar, **Suggest a model from my prompt**. - In the room toolbar: the same accent button, in "no agent" mode, where the task also picks who takes it. - Optionally, the screen can open by itself every time you open an agent (setting below, off by default). Clicking an agent otherwise opens it straight away. ## How to use it 1. Click the sparkle. The screen shows the agent's portrait and one field: "What is this agent going to do?" (or "What are we working on today?" without an agent). 2. Type the task. Scoping blocks appear under the field: **Task complexity (model)** (a rail: **Auto**, **Quick**, **Standard**, **Complex**, **Extreme**), then **Folders involved**, **Reasoning effort** and **Advanced options** (Nature, Intended for, Expected deliverable, Guardrails, free context). Clicking a level yourself opens the session with no network call. 3. Press **Analyze and open** (or Enter). Nothing is sent until then. The result shows three lines, Agent / Model / Session, with **Change** and **Rename**; then **Launch now** (its button pulses gently every few seconds so it is easy to spot; no animation when the system asks for reduced motion), or the session opens by itself depending on the launch setting. 4. **Open directly** under the field skips the analysis and opens the agent exactly as before. The project's terminals bar stays at the bottom of the screen (since 2026-09-28): click a terminal tab, or open a new terminal from it, and the screen closes to show that terminal, without launching any agent. 5. After opening, a thin bar asks once whether the suggested model was right: **It helped**, **Too light**, **Too heavy**. The answer is only sent when usage data sharing is on. The bar disappears once you have sent two messages to the agent: by then you have moved on. **Folders involved** lists the project's folders in a useful order: pinned folders first, then the ones you recently sent on this project, then the rest alphabetically, with build and cache folders (such as `dist`, `build`, `coverage`) last. Ten chips are shown, **Show N more** / **Show less** reveals the others; a ticked chip or one **Suggested by the analysis** always stays visible. Hover a chip (or focus it with the keyboard) to **Pin first** or **Hide** it. Hidden folders leave the list and the analysis; **Hidden (N)** under the chips lets you **Show again**. Pins and hidden folders are saved per project, on your account. ## Settings - `aiSuggestionMode` (global, Settings > Composer, "AI Suggestion", On / Off, default Off): when On, the intent screen opens by itself every time you open an agent instead of waiting for the button. Overridable per project (Project settings > Defaults) and per agent (agent form), each level inheriting from the one above. - `aiSuggestionLaunch` (global, Settings > Composer, "After the suggestion", default "Let me validate"): **Open right away** opens the session as soon as the analysis returns; **Let me validate** shows the decision and waits for **Launch now**. Same project and agent overrides. ## Agent tools (MCP) None. `settings_get` / `settings_set` can read or change the two settings above. ## Providers All providers. No model name is hard-coded: the four levels are resolved from the live catalogue of whichever CLI the agent runs on, from the most capable model down. When a provider offers fewer than four models the table folds upward, so Complex and Extreme both land on the flagship rather than the reverse. When the catalogue ranks every model by strength (Claude, Codex), the levels step through one model per strength tier, and between two models of equal strength the newest generation wins (since 2026-09-26: on Codex the levels used to land on the older GPT-5.6 models while GPT-6 Sol and GPT-6 Luna were skipped). Without any agent CLI installed the screen explains that there is nothing to open. ## Mobile Not available on the mobile companion. ## Limits - Monthly analyses: 25 on Free, 500 on Plus, unlimited on Pro. Without an account: 10 analyses in total. On Free and Plus the agent pool is the room plus the built-in roles; Pro adds the whole expert catalogue. - The description (and scoping fields) is sent to AgentsRoom's servers only when you press Analyze. - Failure never blocks: a dead network, a rate limit or an unusable answer opens the agent on its usual model. Offline, the screen is not shown at all. - The button only appears on an agent without a live session: on a running CLI there is no model left to decide. ## Common questions - **What if I already know how hard the task is?** Click the level on the rail. It becomes your decision, no AI call, the session opens immediately. - **Can it pick the agent too?** Yes, from the toolbar button with no agent fixed: the task chooses among your agents, the built-in roles and, on Pro, the catalogue. - **How do I make the screen appear automatically?** Settings > Composer > AI Suggestion > On. It is off by default; the button is always there. - **The folder list is long and full of folders I never use.** Hide them from the chip's hover bar and pin the ones you use most; the choice is kept for the project. Folders you sent recently already come first. - **Why did the analysis give my task to the QA agent (or the frontend developer) instead of the right one?** The agent choice was tightened on 2026-09-25: an agent or role merely named in your description ("the QA agent hit this bug") is no longer a reason to pick it, a request to review a merge request goes to a code reviewer when one is available, and a screen bug of a mobile app goes to the mobile developer rather than the frontend one. - **Why did a Codex agent get an older GPT-5.6 model for a complex task?** Fixed on 2026-09-26: the levels now pick the current generation (GPT-6 Sol, GPT-6 Luna) when it is as strong as the older one. The provider's default model is unchanged. - **Difference with Adaptive Mode?** Adaptive Mode suggests from the composer draft after the CLI has started; AI Suggestion decides before the session opens. Both use the same sizing policy. ## Related - [Adaptive Mode](https://agentsroom.dev/docs/adaptive-mode.md): the composer-side model suggestion, once the session runs. - [Agent Suggestions](https://agentsroom.dev/docs/agent-suggestions.md): the advisor that only answers "which agent". - [AI Helpers Allowance](https://agentsroom.dev/docs/ai-helpers-allowance.md): monthly allowances of the AI helpers. - [Claude Code Token Usage](https://agentsroom.dev/docs/claude-code-token-usage.md): seeing what a session actually consumes.