Key concepts

A few terms and mechanics come up constantly when using Chat. This page explains each one so the rest of the documentation makes sense.

Sessions

A session is a single conversation thread. Every message you send and every response you receive is part the current session. Sessions are saved automatically — you can return to them later, pick up where you left off, and build on earlier context.

Each session is associated with the agent that was active when the conversation started. The agent's name appears in the session list so you know which one you were talking to.

Chat maintains a full history of your sessions. Start a new session to begin a fresh conversation without affecting the old one.

The selector bar

Before you can chat with an agent, you scope the session by picking a project and an agent from the selector bar at the top of the page.

• Project — the organizational scope that groups your agents. Select the project your agent belongs to.
• Agent — the specific Flows agent to run. The dropdown lists all agents in the selected project.

Once both are selected, the bar collapses out of the way. A banner in the composer area confirms which agent is active and which model it's using.

Chat remembers your last selection. When you return, the previous project and agent are restored automatically.

Meta-Agent mode

Meta-Agent mode is a separate chat mode built into Chat. Instead of talking to one of your Flows agents, you talk to Anter's own Meta-Agent — a specialized agent designed to help you build, configure, and refine other agents through conversation.

While Meta-Agent mode is active:

• The composer placeholder reads Describe the agent you want to build…
• The model selector is hidden (Meta-Agent uses its own model)
• A banner in the composer reminds you to type /meta stop to exit
• Sessions are saved in the browser and persist across page reloads

Meta-Agent mode is independent of your active agent. Entering it doesn't end your current conversation — exiting returns you to the agent you had selected.

The artifact panel

When Meta-Agent generates an agent specification, it appears as an artifact in the conversation — a pill you can click to open the artifact panel on the right side of the screen. The artifact panel shows the full spec content and the controls to create the agent from it.

Artifacts in Chat are persistent. A spec you generated in an earlier session is still accessible from its session in the history.

File uploads

Some agents support receiving files as part of a message — images, PDFs, or documents that the agent can reason about and reference in its response. When an agent supports file uploads, an attachment button appears in the composer.

File upload support is configured per-agent in Flows. If the attachment button isn't visible, the current agent doesn't have file upload enabled.

Permission approvals

If an agent is configured to pause before taking certain actions, a tool approval card appears in the chat. You can approve or deny the action before the agent continues. Approvals expire after five minutes — if no decision is made, the call is skipped and the agent explains what happened.