claude-code - 💡(How to fix) Fix [FEATURE] Allow switching agent configurations mid-session via the /agent menu

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

Right now, the only way to use a specific agent config is to pass --agent <name> at startup. The problem is you have to already know the agent name before you start. That's not always practical — sometimes I want to start a session and then figure out which agent fits what I'm working on.

Proposed Solution

What I'd like:

Augment the existing /agent menu (currently used for spawning subagents) to also support browsing and switching to an agent configuration. I'd want to be able to search through my available agent configs and select one to switch to.

When switching, Claude should prompt me to either preserve the current conversation context or start fresh with the new agent.

This should work for both custom agent specs (.claude/agents/*.md) and built-in agent types.

The --agent flag at startup should stay — this isn't a replacement, just an augmentation to the TUI so the workflow doesn't require knowing the agent name upfront.

Current workaround:

Exit and restart with --agent <name>, which means losing context and needing to remember the exact agent name ahead of time.

Alternative Solutions

The only current workaround is to open claude and use the /agent command to identify the agent I want to use, then exist and restart with the --agent <name> flag.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

1. Open a Claude Code session without specifying an agent upfront.
2. Start working and realize mid-session that a specialized agent would be a better fit.
3. Open the /agent menu and search/browse available agent configurations.
4. Select the desired agent.
5. Choose to either preserve the current conversation context or start fresh.
6. Continue working without needing to exit and restart.

Additional Context

No response