Chat sessions

Every conversation in Chat is a session — a named, saved thread that persists across page reloads. Sessions are created automatically when you send your first message and stored so you can return to them whenever you like.

What a session contains

A session captures the full conversation: every message you sent, every response the agent returned, and any artifacts (like agent specs or documents) that were generated during the conversation. When you reload the page or navigate away and come back, the session reloads exactly as you left it.

Sessions are associated with the agent that was active when the conversation started. The agent name appears alongside the session in the history so you can distinguish conversations across different agents.

The session sidebar

The session history appears in a sidebar panel within the chat interface. From there you can:

• Browse past sessions — see all your previous conversations, most recent first, each titled by its first message
• Open a session — click any session to load it and continue the conversation
• Start a new session — create a blank conversation with the currently active agent
• Delete a session — remove a session and its full history permanently

Session titles

When you send your first message in a new session, the first part of that message becomes the session title. This makes sessions easy to scan when you have many. The title is cosmetic only — it doesn't affect how the session or the agent behaves.

Sessions and agent switching

Sessions are scoped to the agent that was active when they started. If you switch to a different agent — using the selector bar or the /agent slash command — a new session begins for that agent. Your previous session stays in history exactly as it was.

If you return to an earlier session and the agent it was scoped to still exists, that agent is reloaded automatically when you open the session.

Meta-Agent sessions

Conversations with the Meta-Agent work slightly differently. Meta-Agent sessions are stored locally in the browser (not on Anter's servers), so they persist even without signing in, but they're scoped to the device. Clearing browser storage removes them.

Meta-Agent sessions carry additional state — including the agent spec that was generated — so reloading the page while Meta-Agent mode is active restores the full build conversation, spec and all.