Control plane

Agents

Configure who does the work. Every saved setting is read from and written to the PostgreSQL control plane.

Create an agent

Templates are starting points. Their prompts remain editable.

Fixed runtime contract. Structured output, platform tool surface, and message types are applied by the runtime and are not editable here.

Tools and channel

Destination is the provider-specific recipient, such as a Telegram chat ID. It is not an agent name or a workflow ID.

Additional channel fields

JSON object only. Use it for provider-supported keys beyond provider and destination, such as a threadId string.

Interaction rules

Autonomy describes when this agent should pause for human direction. Use a short policy such as “ask-before-risk”; runtime enforcement remains out of scope.

Additional interaction rules

JSON object only. Use this for a schema-supported persisted rule that has no dedicated control.

Guardrails

Cost ceiling is the agent-level budget per run in the control plane’s configured currency unit; it is not a per-request price. The engine refuses a wake once spend reaches the ceiling and pauses the run with a visible system message.

One action per line. Platform tool commands listed here are rejected at the dispatch point and named in the wake prompt.

Additional guardrail fields

JSON object only. Preserve valid nested values here when they do not have a clearer dedicated control.

Memory facts

Facts are stored canonically in this agent’s memory.facts field.

Additional memory details

JSON object only, for canonical memory details beyond individual facts.