runs.*

There is no runs.* JSON-RPC namespace in the current aleph-server runtime. registry.register("runs.*", ...) is never called, no runs handler module exists, and the methods documented in the previous version of this page (run.wait, run.queue_message) are not part of the gateway protocol.

The functionality the previous page implied — waiting for a run to settle, or pushing a message into a live run — is exposed under different names:

• Run state: chat.send / chat.abort / agent.run / agent.cancel. A subscriber to the agent.* topic on the event bus sees agent.started, agent.completed, agent.error, and the per-turn stream.agent_trace events.
• In-run steering: incoming Steer messages on the originating channel (default) are injected into the live event log and consumed at the next turn boundary. The bus handles fan-out; there is no separate "queue" RPC.
• HITL approval for a run: the exec.approval.resolve and clarification.resolve RPCs (one-card-per-prompt) are the only legal in-run interaction surface.

The previous version of this page described run.wait and run.queue_message as if they were real. They are not, and writing client code against them will return Method not found (-32601).

What exists

The closest analogues on the wire:

• agents.* — the per-run lifecycle RPCs (start, status, cancel, abort) under /docs/en/gateway/methods/agent.
• subagent.tree — snapshot the live background sub-agent tree ({ "nodes": [...], "count": N }).
• chat.send — start a chat turn; the response carries a run_id you can correlate against the event bus.

See Also

• Methods Reference -- All currently registered namespaces
• agent.* -- Run lifecycle (start / status / cancel / abort)
• chat.* -- Chat turn transport and the run_id it returns
• events.subscribe -- Subscribe to agent.* / stream.* topics for live run state