Octoloom Chat Sessions
An Octoloom chat session is an exploratory session that opens a chat window instead of the A2D tester. People you invite chat with an A2A agent, such as an Octoloom broker, and mark each reply Passed, Failed or Not completed. Everything they do is stored in A2D, even when nobody has the session open.
Octoloom chat sessions only change exploratory sessions in A2D. The standalone A2 Playground (web and desktop) is not affected.
How It Works
- In Octoloom for Agent Fabric (VS Code), you share a broker and invite people by email. Octoloom creates an exploratory session in A2D with
session_type: "octoloom_chat"through the A2D Platform MCP. Sessions Octoloom shares withoutsession_typeare recognised by Octoloom’s description (“Chat with the … broker … (shared from Octoloom).”) and also open the Octoloom chat. - Each invited person gets an email with a link to
/explore/<token>. - They sign in with a 6-digit code sent to their email. The code is valid for 10 minutes and allows 5 tries.
- They chat with the broker. Their messages go to the A2D server, which calls the broker with the environment’s credentials. The browser never sees the credentials.
- They mark replies, add comments and submit the session with the submit icon. A2D records the result as an exploratory run.
- Octoloom (or any MCP client) reads the conversations, marks and runs back with
get_exploratory_session_results.
Session Types
session_type | Visitor sees | Used for |
|---|---|---|
a2tf (default) | The A2D tester with assets, entities and per-entity feedback | MCP servers, agent cards and REST APIs |
octoloom_chat | The Octoloom chat window only | One A2A agent (an Octoloom broker) |
Both types share invites, sign-in, feedback, captured data and Submit. Existing sessions are a2tf. Only Octoloom sessions open the Octoloom chat. Every other exploratory session keeps the A2D tester. Both types count as exploratory sessions in A2D’s statistics, including Total Exploratory Sessions on the landing page.
Creating a Session over MCP
Use create_exploratory_session with session_type and the octoloom settings. broker is required.
{
"name": "Incident assistant review",
"expires_at": "2026-12-01T00:00:00Z",
"session_type": "octoloom_chat",
"octoloom": {
"broker": "incident_broker",
"title": "Incident Assistant",
"protocol": "1.0",
"allowFeedback": true,
"allowSessionFeedback": true
}
}Then add the broker’s agent card with add_asset_to_session, pick its environment, and invite people with add_invite_to_session. The invite email is sent by default. Pass send_email: false to skip it.
The Chat Page
The chat page looks like Octoloom’s own chat portal, with the Octoloom mascot and colours. The sign-in and code screens use the same style.
-
Header — the Octoloom mascot, the broker title, an
A2A <protocol>pill and a status dot that is green when the agent card answers. The actions are icons only:Icon Action History Show or hide the conversation history Plus Start a new conversation. The previous one stays in the history. Message Show or hide the feedback sidebar Upload Submit the session -
History (left) — your earlier conversations, newest first. Click one to reopen it. It collapses to a thin rail.
-
Empty state — the broker’s skills from its agent card. Click an example to send it.
-
Replies — each reply shows its task state (Completed, Needs input, Failed, …), how long it took, a copy icon and a feedback icon. The feedback icon opens the sidebar on that reply.
-
Continuing a task — when the broker asks for more input, your next message continues the same task.
The Feedback Sidebar
The sidebar on the right collapses to a thin rail and has two parts:
- Overall status — mark the whole session Passed, Failed or Not completed, and add a comment. This is saved as you go.
- Captured data — one entry for each message of the open conversation, captured automatically. Each entry shows the task state, HTTP status, duration, task id and time, and the request and response bodies. Secrets, headers and URLs are removed. Mark each reply Passed, Failed or Not completed and add a comment.
Submitting the Session
The submit icon, in the header and in the sidebar, opens a dialog with:
- counts of conversations, messages, rated replies and comments;
- your reply marks and comments, with the captured data;
- the session status, Passed or Failed (required), and an overall comment.
The submit icon sends the feedback. After that the chat is read-only for you.
The page follows your system light or dark theme.
Broker Authentication
The A2D server adds the environment’s auth to every call to the broker. The supported environment auth_type values are:
auth_type | auth_config | Sent as |
|---|---|---|
none | — | Nothing |
bearer | { "token" } | Authorization: Bearer … |
basic | { "username", "password" } | Authorization: Basic … |
client_credentials | { "token_url", "client_id", "client_secret", "scope?", "audience?" } | A token fetched on the server, cached, and refreshed once on a 401 |
header | { "name", "value" } or { "headers": { … } } | The given headers, for example Client ID Enforcement |
Stored request and response snapshots have secrets removed, but the environment’s auth_config itself is stored as entered. Use credentials scoped to the broker.
Reading the Results
get_exploratory_session_results returns everything for one session, for both session types:
{
"session": { "id": "…", "session_type": "octoloom_chat", "status": "active" },
"summary": { "invited": 3, "verified": 2, "submitted": 1, "messages": 14, "passed": 6, "failed": 2, "in_progress": 1, "failed_replies": 1 },
"invites": [ { "email": "a@example.com", "status": "submitted", "verified_at": "…", "submitted_at": "…", "messages": 9 } ],
"feedback": [ { "email": "a@example.com", "entity_type": "reply", "entity_name": null, "status": "passed", "comment": "…" } ],
"conversations": [ { "email": "a@example.com", "context_id": "…", "turns": [ { "message_text": "…", "reply_text": "…", "task_state": "completed" } ] } ],
"runs": [ { "email": "a@example.com", "passed": 6, "failed": 2, "in_progress": 1 } ]
}since(optional) returns only activity after a timestamp.include_snapshots: trueadds the redacted request and response bodies.- Long text is cut at 4,000 characters and marked
truncated: true.
get_exploratory_session also returns invites (with verified_at and submitted_at), feedbacks and runs. For a2tf sessions this means the marks and comments testers set on tools, resources, prompts, skills and endpoints now reach the owner over MCP, with entity_name filled in when it is known. list_exploratory_feedbacks and list_exploratory_interactions page through the raw rows (50 by default, up to 200).
Limits
- 30 messages per minute and 500 per day for each person.
- Messages up to 8,000 characters.
- The broker has 120 seconds to answer.
Next Steps
- Exploratory Testing — Sessions, invites and the A2D tester.
- Agent Cards — Describe the broker you share.
- Test Lab — See exploratory runs next to your other runs.
Share an Octoloom broker with a link, and every conversation and rating lands in A2D.