Skip to main content
Client creates executions and inspects what they did. Your backend, a script, or an operator uses it, not the agent handler.
baseUrl is required, from the option or REBUNO_URL. apiKey is optional and sent as Authorization: Bearer ... when present.

Executions

create and get return an Execution. Poll get or read the event log to watch it progress.

Event log and steps

Read the raw event stream, or the steps it produced:
events is paginated by afterSeq: pass the last eventSeq you’ve seen. limit defaults to 100.

Approvals

When policy requires approval for a step, the execution blocks and an approval is created. Inspect and resolve them through Client:
Granting an approval lets the kernel re-dispatch. The handler replays its recorded steps and proceeds past the one that was waiting. From the handler’s perspective the blocked call simply returns once approved.

Errors

Failed requests throw typed errors: NotFoundError, UnauthorizedError, ForbiddenError, ValidationError, PolicyError, NetworkError, and others, all subclasses of RebunoError. See Errors.

Types

Client returns plain objects with camelCase fields.
  • Execution: id, agentId, input, status, output, failureReason. status is an ExecutionStatus, one of pending, running, blocked, completed, failed, cancelled.
  • Step: stepId, executionId, kind, target, argsHash, occurrence, status, idempotency, args, result, error.
  • Event: executionId, eventSeq, type, payload, occurredAt.
  • Approval: id, stepId, executionId, status, message, decidedBy, rationale.
All are exported as types from rebuno.