Hanzo
Cloud MCPagents

post_v1_agents_sessions

RegisterSession opens a live agent session in the caller's org — the row every surface (the CLI's outer agent, hanzo.bot, the console, chat) hangs its activity off.

RegisterSession opens a live agent session in the caller's org — the row every surface (the CLI's outer agent, hanzo.bot, the console, chat) hangs its activity off. A session with a parentSessionId becomes a subagent of that session and inherits its root, so one flow is one tree; without one it is itself a root. Registering with a terminal status records a session that has already finished.

Toolpost_v1_agents_sessions
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments16
OperationPOST /v1/agents/sessions
Productagents

Arguments

FieldTypeRequiredDefaultDescription
accountstring
actorstring
agentstring
cwdstring
hoststringExecution context — where this session runs (all optional).
parentSessionIdstring
projectstringThe readable build (provenance.go): which product this session builds, and whether its story may be read by the world.
providerstringAccount tag — the linked AI account this session ran under (login manager).
publishedboolean
repostring
statusstring
targetstring
taskRunIdstring
taskWorkflowIdstring
terminalstringTerminal is the URL this session's live terminal is published at, so the console can watch it. Optional — a session that publishes nothing is still a session.
titlestring

This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "post_v1_agents_sessions",
         "arguments": {
           "account": "<account>",
           "actor": "<actor>",
           "agent": "<agent>",
           "cwd": "<cwd>",
           "host": "<host>",
           "parentSessionId": "<parentSessionId>",
           "project": "<project>",
           "provider": "<provider>",
           "published": false,
           "repo": "<repo>",
           "status": "<status>",
           "target": "<target>",
           "taskRunId": "<taskRunId>",
           "taskWorkflowId": "<taskWorkflowId>",
           "terminal": "<terminal>",
           "title": "<title>"
         }
       }
     }'

Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

OperationRouteProductSummary
cloud_post_v1_agents_sessionsPOST /v1/agents/sessionsagentsRegisterSession opens a live agent session in the caller's org — the row every surface (th

The same capability over plain HTTP is in the agents API reference, on https://api.hanzo.ai.


All 834 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page