PacketAgentDocs

PacketAgent#

PacketAgent is a self-hosted control plane for long-running automation Workers. An operator defines versioned Worker behaviour, deploys an immutable version, chooses how it is triggered, limits the tools it may use, and reviews the run record and artifacts afterward.

What a Worker contains#

A Worker separates identity from executable content:

  • the definition gives the Worker its stable name and ownership;
  • a version contains instructions, model routing, tools, triggers, budgets, retries, and exit conditions;
  • a deployment binds one version to an environment and compiled permission policy; and
  • a run records one execution with events, checkpoints, usage, approvals, and artifacts.

Versions are immutable after they are frozen. Deploy a new version when behaviour changes rather than editing a running release in place.

How Workers start#

PacketAgent supports manual, cron, webhook, queue, and alert trigger declarations. Manual, cron, webhook, and configured alert delivery are the normal operator-facing paths. A declared trigger is not proof that an external event source has been connected; verify every trigger with a real delivery.

Safety model#

Tool capabilities are allowlisted and bound into the deployment. Actions may require approval, and run budgets cap turns, tokens, time, or provider cost when the selected model has pricing data.

Generated code execution should use the Docker sandbox in production. Keep the application and generated-app preview on different HTTPS origins, mount durable storage, and supply explicit production secrets.

Next#