Module assistant 

The built-in assistant: the embedded AWL document, its boot install, and the description the server serves of it. The built-in assistant: a server-owned agent session, present the moment aion server runs.

This is the ops-console doctrine applied to an agent. The console is compiled into the binary and served at / with no operator step; the assistant is the same — the agent harnesses ship in the binary as a catalogue (aion_integration_acp::catalogue), a session is opened from the console, and the server owns the harness process for its lifetime. There is no document to deploy, no worker to start, and no configuration to write: a stock cargo install aion-cli therefore carries the assistant.

The brain is a seam, not a dependency

Nothing here names one agent. WHICH harness serves a session is the operator’s pick from the shipped catalogue, made per session in the console and remembered per caller; every launch setting is the catalogue entry’s own. This module describes the surface, mints the session credential, and drives the process; it never decides which brain answers.

What lives here

• [descriptor] — what GET /assistant says: the catalogue with this machine’s availability reading, the tool wiring a session is handed, whether sessions can be opened, and the reading caller’s grant standing.
• [sessions] — the live harness processes, their durable transcripts, and the surface that drives them.
• mcp — the assistant-only MCP route: the tools about one conversation, behind that session’s own server-minted bearer.
• grounding — the version-true Aion and AWL reference pack every spawned agent is pointed at.

Re-exports

pub use descriptor::AssistantDescriptor;

pub use descriptor::AssistantGrantDescriptor;

pub use descriptor::AssistantHarnessDescriptor;

pub use descriptor::AssistantOwnToolsDescriptor;

pub use descriptor::AssistantSessionTokenDescriptor;

pub use descriptor::AssistantToolsDescriptor;

pub use descriptor::describe;

Modules

descriptor

What the server says about the assistant it carries.

mcp

The assistant-only MCP route: the tools about one conversation, behind the session’s own bearer. The ASSISTANT-ONLY MCP surface: /assistant/mcp.

sessions

Server-owned assistant sessions: the live harness processes, their durable transcripts, and the surface that drives them. Server-owned assistant sessions: one live agent-harness process per caller conversation, with a durable transcript and a live socket.