Agent

3 actions. Each is callable by the agent as a tool, over HTTP via /api/invoke, and (usually) from a UI page.

agent.tick

POST · mutating

Run one tick of the agent loop for a mission. The agent decides whether to scan trends, draft, respond, refresh knowledge, or idle.

• AI tool: agent_tick
• API: POST /api/invoke/agent.tick

Input

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "id"
  ]
}

agent.run_get

GET

Get the status of a durable agent run by id. The chat client polls this to detect when a server-resumed turn has finished.

• AI tool: agent_run_get
• API: GET /api/invoke/agent.run_get

Input

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "id"
  ]
}

agent.runs_active

GET

Get the latest still-running (queued or running) durable agent run for a conversation, or null. The chat client polls this on mount / after a stream error to detect a turn still being worked server-side (e.g. resumed by the sweeper after a restart).

• AI tool: agent_runs_active
• API: GET /api/invoke/agent.runs_active

Input

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "conversationId": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "conversationId"
  ]
}