Agent Morphing

  • Desktop, mobile and web
  • All plans
View as MarkdownFeature page

What it does

Switch a running agent's role on the fly without restarting it and without losing anything it knows. A role-change prompt is injected into the live session, the agent acknowledges in a sentence and carries on with its new specialty: the Product Manager who just finished the analysis becomes the Fullstack developer who implements it, then the QA who verifies it, in the same conversation. The agent's identity changes everywhere at once (avatar, colour, name, sidebar, tab) and a morph trail records every role traversed.

Video (1 min): Agent Morphing, shown in the real app. A developer agent fixes a bug, is switched to Security Engineer in one click, and reviews its own fix with the whole conversation still in memory.

Where to find it

  • Desktop: the role chip in the agent's terminal header, labelled Morph agent in its tooltip ("Currently {role}. Click to switch role on the fly"), with up/down chevrons like the model selector.
  • Mobile: open the agent's console and tap the role pill in its header (Morph the agent), under the spec strip, exactly like the desktop chip; or the manage menu, then Morph agent ("Switch role live, the session context is kept").

How to use it

  1. Click the role chip. The Morph agent overlay opens with only the agent picker: search, Core Team / Specialists, Experts (The Agency) and Community. No model, provider or advanced options.
  2. Pick the target role. The header shows the morph trail (for example PM to Fullstack to QA).
  3. Options: Fresh eyes (the agent re-evaluates the work critically, verifies instead of assuming; ticked by default for QA and Security) and Switch to the role's default model (only offered when the CLI can change model live, applied with the CLI's own model command, no restart).
  4. Click Morph. If the agent has a live session, the switch is injected and the agent continues. If it is idle, the new role is saved and applies at its next launch.

Settings

None.

Agent tools (MCP)

None. Morphing is a user gesture; agents_save edits an agent's saved role and prompt but does not inject a live role change.

Providers

All providers: the role prompt is injected into the live console whatever the CLI. Adopting the role's default model live is only offered on CLIs that support switching model in-session; elsewhere the model is unchanged. Morphing never changes the provider; that stays the job of the model pill or the agent's edit form.

Mobile

Present. The role pill of the console header opens the same picker (search, roles, Experts, Community) with the Fresh eyes option; the morph runs on the desktop session. The manage menu's Morph agent entry still opens it too.

Limits

  • The Custom role (persona you write yourself) is not a morph target; use the agent's edit form for that.
  • Very long expert personas are truncated when injected, so the session keeps responding.
  • Morphing an agent driven by a live Agent Team run works, but the run's next step may rewrite its identity.
  • An earlier manual rename does not survive a morph: the agent takes the new role's name.

Common questions

  • What is the difference with spawning a new agent? A new agent starts blank and needs everything re-explained. A morphed agent keeps the whole session, history and decisions.
  • Does the agent keep its conversation? Yes, entirely. Only the role, its persona and its visual identity change.
  • When should I use Fresh eyes? When morphing into QA, Security or any review-type role: the agent keeps its knowledge of the code but drops its attachment to what it just wrote.
  • The agent is idle, can I still morph it? Yes. The new role is saved and used the next time you open it.
  • Is there a video that shows it? Yes, one minute, filmed in the real app: https://youtu.be/GQFLkklPMTQ

Related