Chat
2 actions. Each is callable by the agent as a tool, over HTTP via /api/invoke, and (usually) from a UI page.
chat.session_get
GET
Get the active floating-chat conversation id for the current user actor. Synced server-side so the same thread opens on every device.
- AI tool:
chat_session_get - API:
GET /api/invoke/chat.session_get
Input
| Field | Type | Required | Description |
|---|---|---|---|
actorId |
string | — |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"actorId": {
"type": "string",
"minLength": 1
}
}
}chat.session_set
POST · mutating
Persist the active floating-chat conversation id for cross-device sync.
- AI tool:
chat_session_set - API:
POST /api/invoke/chat.session_set
Input
| Field | Type | Required | Description |
|---|---|---|---|
actorId |
string | — | |
conversationId |
union | yes |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"actorId": {
"type": "string",
"minLength": 1
},
"conversationId": {
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "null"
}
]
}
},
"required": [
"conversationId"
]
}