Concepts

Agent sessions

An agent session is a durable conversation with one agent. Sessions are useful for ad-hoc work, coaching, debugging, or built-in messaging flows that should not advance an automation run.

Sessions are separate from automation runs:

Surface	Use it for
Automation run	A versioned process with steps, concurrency, triggers, and run events.
Agent session	Open-ended conversation history and live generation events.
Interaction	A structured approval, review, or information request.

Durable transcript and live events

The session transcript is durable. Live events are streamed over SSE:

mobius agents stream-session-events agt_triager ses_01...

The live stream carries ephemeral events such as generation deltas. The messages endpoint remains the source of truth for the transcript.

Channel turns

When an agent is connected to a messaging provider such as Slack or Telegram, inbound messages can create channel turns. A channel turn records provider routing, delivery status, session lookup, and the resulting agent response.

Channel turns let operators answer:

Did the provider event reach Mobius?
Which session did it route to?
Did the agent reply?
Was the reply delivered back to the provider?

Some channel-turn inspection endpoints are internal, but the model is important when debugging messaging behavior.

Inboxes

Agents can opt into an email inbox:

mobius agents provision-inbox agt_triager

The agent receives an email_address. Mail sent to that address can emit email.received source events and can be used by messaging flows. Treat email content as untrusted external input.

Messaging bindings

Messaging bindings connect an agent to a provider account and define which conversations activate the agent:

Direct messages.
Mentions.
All messages in selected channels.
Sender allowlists.
Conversation allowlists.
Per-binding model route.

Use narrow bindings first. It is easier to widen a useful agent than to untangle a noisy one.

Sessions in automation steps

Automation agent steps can use session policy to reuse or isolate conversation context. Use a run-scoped session when the agent should remember earlier steps in that same run. Use a fresh turn when each execution should stand alone.

Agents define the agent identity and default model behavior.
Source events includes session.message.created and email.received.
Interactions are structured requests, not open-ended chat.
Runs are the automation execution surface.