bernstein_run
Submit a goal to queue a multi-agent orchestration run and receive IDs to poll until completion.
Instructions
Start an orchestration run by posting a task to the Bernstein server.
A run executes real work and takes minutes to hours. This call
returns as soon as the run is queued, not when it finishes. Do not
re-issue it while waiting: that starts a second run. To follow the
run, wait poll_after_ms and then call bernstein_run_status,
passing either the returned task_id or the returned run_id.
Poll it until status is terminal (completed, failed or
cancelled).
Args:
goal: Description of what you want Bernstein to accomplish.
role: Specialist role to assign (backend, frontend, qa, security, …).
priority: 1=critical, 2=normal, 3=nice-to-have.
scope: Task scope - small, medium, or large.
complexity: Task complexity - low, medium, or high.
estimated_minutes: Rough time estimate in minutes.
parent_task_id: When set, the run is created as a subtask of this
task, and the parent transitions to waiting_for_subtasks.
Returns:
JSON with the created task ID, title and status, plus the
run_id naming the run journal and the advisory
poll_after_ms delay before the first poll. When the call
itself is task-augmented (the client sent task in the request
params), a Tasks-extension CreateTaskResult is returned
instead so the client can poll the run.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal | Yes | ||
| role | No | ||
| scope | No | ||
| priority | No | ||
| complexity | No | ||
| parent_task_id | No | ||
| estimated_minutes | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| _meter | Yes | ||
| result | Yes |