slaunt
DOCUMENTATION

Lifecycle tools

These tools create threads and runs and keep Quaero current. With Claude Code or Codex hooks installed you rarely call them yourself; elsewhere the model calls them every turn. Which call is valid when is covered in Lifecycle. Every call returns a runtime snapshot (fields at the end of this section).

thread_begin

Call once at the start of a chat.

ParamType
request_idstring ≤256Required. New per attempt, reused on retry.
new_threadbooleanRotate from an idle thread into a new chat on the same connection
labelstringShown for the thread
metadataobject

Returns ok, the server-minted thread_uuid, thread_resolution_source and runtime.

run_begin

Call when you start a task. task is what Quaero shows as the agent's activity, so make it specific ("Fix flaky login test", not "Working").

ParamType
taskstringRequired
request_idstring ≤256Defaults to the JSON-RPC id
metadataobject

run_step

Call at real milestones: a file done, tests passing, waiting on input. It updates Quaero and closes any telemetry gap.

ParamType
activitystringRequired. Replaces the activity text in Quaero.
detailsstring
progressnumber 0–100Drives the progress bar
spend_usdnumber ≥0Running spend estimate for the run
request_id, metadata

run_end

ParamType
outcomecompleted | errored | interrupted | killedDefault completed. Use killed/interrupted after a stop.
summarystring
resultany JSONFinal output payload
request_id, metadata

thread_close

Marks the whole chat finished; only valid between runs. Params: reason, request_id. Not needed after every task.

runtime snapshot

Field
thread_state, thread_state_versionCurrent state and its version
run_active, active_run_uuid
current_activityWhat Quaero shows
client_key, client_labelDetected client, e.g. claude-code
stop_requested, stop_requested_atSet when someone stops the agent
last_run_begin_at, last_run_step_at, last_run_end_at
telemetry_gap_open, telemetry_gap_countWhether the run currently looks stale