[ux] Analyst mode silently blocks write actions instead of prompting to switch modes

[shreyastelkar]

Problem

Analyst mode enforces strict read-only access — "No file writes. Cannot modify your codebase." This is correct by design, but it silently blocks expected side-effects like saving warehouse credentials (warehouse_add), writing memory blocks, or updating config files. The user gets a refusal with no guidance on how to proceed.

Expected behavior

When the agent in analyst mode encounters a necessary write action, it should prompt the user:

"This action requires builder mode (saving warehouse credentials). Switch to builder mode now? [y/n]"

Then either auto-switch or provide a one-command instruction.

Current behavior

The agent silently refuses or explains that it cannot perform write actions in analyst mode. The user must:

1. Know that builder mode exists
2. Know how to switch to it
3. Manually switch, then re-issue the request

This is especially frustrating during /discover workflows in analyst mode — the agent can scan and detect connections but cannot save them.

Additional context

• Agent modes docs document analyst as "SELECT only, no file writes"
• The friction is not the restriction itself — it is the lack of a smooth escape hatch
• Related: plan mode also does not auto-switch (separate issue)