Create the first Worker#
This procedure creates one versioned Worker, validates it, deploys it, and runs it manually. Use a harmless prompt and no external write tools for the first execution.
Before you start#
- Sign in to a ready PacketAgent installation.
- Confirm one provider model resolves successfully.
- Start Docker when the deployment requires sandbox validation.
- Choose a workspace where test run records may be stored.
Create the definition#
- Open Workers and create a definition.
- Give it a stable name and a narrow purpose, such as summarising supplied text.
- Save the definition before adding a version.
The definition is identity. Put executable behaviour in the version so later changes produce an auditable version history.
Add and validate a version#
- Create a version under the definition.
- Write instructions that describe one output.
- Select a model routing preset.
- Add a manual trigger.
- Set small turn, token, time, and cost budgets.
- Leave write-capable tools disabled.
- Add an exit condition that recognises the completed output.
- Run validation and resolve every blocking result.
Freeze the version only after validation succeeds. A frozen version is immutable.
Deploy and run#
- Create a deployment from the frozen version.
- Review the compiled trigger and permission summary.
- Activate the deployment.
- Use Run now with a small input payload.
- Open the run detail while it executes.
Verify#
A successful first Worker demonstrates all of these:
- the deployment is active and points to the intended version;
- the manual trigger creates exactly one run;
- events progress through model execution to a terminal status;
- the run remains within the configured budgets;
- the output and any artifact are readable from the run detail; and
- no tool or approval was requested outside the declared policy.
If it does not work#
| Symptom | Action |
|---|---|
| Version cannot be frozen | Resolve validation errors and make every required trigger, budget, and exit field explicit. |
| Deployment cannot activate | Confirm the version is frozen and the compiled policy is valid. |
| Run remains queued | Check scheduler leadership and the active store. |
| Provider call fails | Test the credential and selected model preset. |
| Run exhausts its budget | Narrow the task or raise one reviewed limit at a time. |
Next#
- Triggers, permissions, and approvals — add controlled automation.
- Run operations — monitor and recover production runs.