patch_v1_agents_sessions_id
PatchSession updates a session's surface-owned truth: its status, its title, the run-target it is dispatched to, and the product it built plus whether that build's story is public.
PatchSession updates a session's surface-owned truth: its status, its title, the run-target it is dispatched to, and the product it built plus whether that build's story is public. A FINISHED session stays finished — reopening a done/error run would fabricate liveness — and publishing is refused unless the session names the project it built, because the public build route is keyed on (org, project).
| Tool | patch_v1_agents_sessions_id |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 7 |
| Operation | PATCH /v1/agents/sessions/{id} |
| Product | agents |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
id | string | — | — | ID is the session to update, from the path. |
project | string | — | — | Project tags the product this session built; Published is the author's decision to let anyone read the story (provenance.go). Both are pointers so "absent" and "cleared" are different requests. |
published | boolean | — | — | — |
status | string | — | — | — |
target | string | — | — | Target re-dispatches a session to a run-target (the #48 association). "" detaches. |
terminal | string | — | — | Terminal publishes (or, with "", withdraws) the URL this session's live terminal can be watched at. A pointer so "absent" and "withdrawn" are different requests: a session that stops sharing must be able to say so. |
title | string | — | — | — |
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": "patch_v1_agents_sessions_id",
"arguments": {
"id": "<id>",
"project": "<project>",
"published": false,
"status": "<status>",
"target": "<target>",
"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
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_patch_v1_agents_sessions_id | PATCH /v1/agents/sessions/{id} | agents | PatchSession updates a session's surface-owned truth: its status, its title, the run-targe |
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?