---
title: Switch agents and models
description: Change agent or model mid-session, and what carries over.
section: Guides
order: 7
---

# Switch agents and models

One Admiral session can run on different agents and models over its life. You switch from the composer picker; the transcript stays.

## What switching means

Two cases behave differently:

**Same agent, different model.** The session resumes normally with the new model. Nothing is lost.

**Different agent.** A switch to a different agent starts a fresh native session under the hood. Admiral hands the new agent a compact summary of verified project facts so it can continue usefully. The visible transcript stays in place.

What does **not** carry across an agent switch:

- The agent's hidden reasoning.
- Tool state inside the old agent.
- Anything the old agent knew but never wrote into the transcript.

The new agent knows what the transcript shows, plus the handoff summary. When a switch loses something important, paste the missing context into the composer.

## The agents

| Agent | Models |
| --- | --- |
| Claude Code | Claude models. |
| Gemini | Gemini models, on Antigravity. |
| OpenCode | OpenCode models, including the built-in free models. |

## Enable agents and manage sign-ins

The Providers settings page owns this:

- Sign in to each provider from its card.
- Turn agents on or off for the pickers.
- Watch usage meters, which warn at 80 percent and again at 95 percent of a limit, with the reset time.

See [Settings pages](../reference/settings.md).

## Sessions from earlier agents

Sessions that earlier versions of Admiral ran on other agents stay readable.

## Next steps

- [Agents and models](../concepts/agents-and-models.md): the concepts behind this guide.
- [Steer and queue](steer-and-queue.md): send, steer, and queue.