job
job.complete
job.complete
Effects: write
Mark the job as completed. This sanitizes PII from the context and records a completion summary. Use when all tasks in the job are done.
Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
job_id | integer | no | Omit it: the run's own job is used. |
summary | string | no | Brief summary of what was accomplished |
job.escalate
job.escalate
Effects: write
Escalate the job to a human. Use when you cannot resolve an issue, someone is not responding, or a situation requires human judgment.
Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
job_id | integer | no | Omit it: the run's own job is used. Never pass a thread or message id here. |
reason | string | yes | Why escalation is needed |
job.read_context
job.read_context
Effects: write
Read the current job context. Returns the full state of your active job including assignments, escalations, and any data you previously stored.
Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
job_id | integer | no | Omit it: the run's own job is used. |
job.update_context
job.update_context
Effects: write
Update the job context by merging new data. Existing keys are preserved unless explicitly overwritten. Use this to record progress, update assignment statuses, or store intermediate results.
Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
job_id | integer | no | Omit it: the run's own job is used. |
updates | object | yes | Key-value pairs to merge into job context |