pi-herdsman 0.1.4 → 0.2.0

package/docs/reference/{worker.md → agent.md}

@@ -1,8 +1,8 @@
-# `worker` API
+# `agent` API
 
 [Documentation index](../README.md) · [supervision reference](supervision.md)
 
-`worker` is the structured model-facing API for managed workers. It has exactly six actions:
+`agent` is the structured model-facing API for managed agents. It has exactly six actions:
 
 ```text
 list
@@ -14,7 +14,7 @@ inspect
 ```
 
 Unknown fields and unsupported selector combinations fail with `invalid_request`.
-The tool is registered only for the lead controller and authorized delegating worker
+The tool is registered only for the lead controller and authorized delegating agent
 controllers.
 
 ## `delegate`
@@ -35,12 +35,12 @@ Every variant rejects additional properties.
 
 Allowed fields are `action`, `definition`, `task`, optional `label`, `cwd`,
 `files`, `fork`, and `timeoutMs`. The definition is resolved from
-the effective roster and delegating worker controllers may use only their allowlisted
+the effective roster and delegating agent controllers may use only their allowlisted
 definitions. Project definitions still require trusted project approval.
 `fork`, when supplied, is an exact saved Pi session path or full UUID used as
 the source for a new derived context; otherwise a new Pi session is launched.
-Each accepted definition delegation creates one worker generation for one
-assignment. The terminal result is delivered once and the worker is cleaned up.
+Each accepted definition delegation creates one agent generation for one
+assignment. The terminal result is delivered once and the agent is cleaned up.
 
 ### Session
 
@@ -52,19 +52,26 @@ assignment. The terminal result is delivered once and the worker is cleaned up.
 }
 ```
 
-Allowed fields are `action`, `session`, `task`, optional `files`, and
+Allowed fields are `action`, `session`, `task`, optional `label`, `files`, and
 `timeoutMs`. The exact saved session supplies its cwd, definition identity, and
-historical Pi context. Session delegation always creates a new worker generation
-for one assignment; it never assigns work to an existing worker. The saved
-definition must currently resolve to an enabled, authorized effective
-definition, whose current configuration is used for the new generation.
+historical Pi context. Session delegation always creates a new agent generation
+for one assignment with a live label; it never assigns work to an existing
+agent. The saved definition must currently resolve to an enabled, authorized
+effective definition, whose current configuration is used for the new
+generation.
 Concurrent or otherwise conflicting managed representations of the exact
 session fail closed. The controller's own active Pi session cannot be delegated
 to itself; use definition delegation with `fork` when a separate derived
 context is required.
 
+`label` is optional on both delegation variants and identifies the live
+generation, not the continuation session. When omitted, Herdsman chooses a
+fresh available label derived from the effective agent definition. An explicit
+label is used exactly as the live label; if that label is occupied, delegation
+fails with `agent_label_exists`.
+
 All successful delegation results use `action: "delegate"` and include
-`worker`, `definition`, request, session, and startup evidence where available.
+`agent`, `definition`, request, session, and startup evidence where available.
 Delegation returns after durable acceptance, not completion. A terminal result
 also makes the exact session identity prominent so it can be used with a later
 `delegate.session` call.
@@ -78,54 +85,63 @@ Request:
 ```
 
 No selectors or other fields are accepted. A successful result includes the
-effective `agent_definitions` roster and visible worker records.
-
-Each actionable live worker record includes:
-
-| Field                                                           | Meaning                                                                                                                               |
-| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| `worker`                                                        | Exact live logical worker identity to copy into `steer.worker`, `reply.worker`, or `close.worker`. It is not a continuation identity. |
-| `state`                                                         | Safe lifecycle state for observability.                                                                                               |
-| `available_actions`                                             | Snapshot of operations currently eligible for this controller.                                                                        |
-| `workspace_id`, `pane_id`, `tab_id`, `tab_label`                | Herdr identity evidence.                                                                                                              |
-| `cwd`, `pi_session_id`, `pi_session_path`                       | Worker location and Pi session evidence.                                                                                              |
-| `owner_session_id`                                              | Exact direct owner Pi session.                                                                                                        |
-| `agent_definition`                                              | Effective definition name.                                                                                                            |
-| `active_request_id`, `last_activity_at`, `stale`, `inactive_ms` | Assignment and advisory activity evidence.                                                                                            |
-| `parent_label`, `orphan`                                        | Visible direct-owner ancestry and proven orphan recovery evidence.                                                                    |
-| `cleanup_error`, `result_error`, `diagnostic`, `tokens`         | Bounded recovery and presentation evidence when present.                                                                              |
+effective `agent_definitions` roster and visible agent records.
+
+Each actionable live agent record includes:
+
+| Field                                                           | Meaning                                                                                                                           |
+| --------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `agent`                                                         | Exact live logical agent identity to copy into `steer.agent`, `reply.agent`, or `close.agent`. It is not a continuation identity. |
+| `state`                                                         | Safe lifecycle state for observability.                                                                                           |
+| `available_actions`                                             | Snapshot of operations currently eligible for this controller.                                                                    |
+| `workspace_id`, `pane_id`, `tab_id`, `tab_label`                | Herdr identity evidence.                                                                                                          |
+| `cwd`, `pi_session_id`, `pi_session_path`                       | Agent location and Pi session evidence.                                                                                           |
+| `owner_session_id`                                              | Exact direct owner Pi session.                                                                                                    |
+| `agent_definition`                                              | Effective definition name.                                                                                                        |
+| `active_request_id`, `last_activity_at`, `stale`, `inactive_ms` | Assignment and advisory activity evidence.                                                                                        |
+| `parent_label`, `orphan`                                        | Visible direct-owner ancestry and proven orphan recovery evidence.                                                                |
+| `cleanup_error`, `result_error`, `diagnostic`, `tokens`         | Bounded recovery and presentation evidence when present.                                                                          |
 
 `available_actions` is authoritative model guidance for the current snapshot.
 Do not infer eligibility from `state`. Active work may list `steer`; a valid
 correlated pending `ask_owner` may list `reply`; exact direct ownership may list
-`close`. `available_actions` never lists `delegate`: a worker cannot receive a
+`close`. `available_actions` never lists `delegate`: an agent cannot receive a
 second assignment. Descendant visibility does not grant control. Lead orphan
 recovery may expose only `close`. Unknown and recovery-only records are
 non-actionable. Every operation rechecks identity, ownership, mailbox state, and
 lifecycle immediately before mutation.
 The public record does not expose `steerable`.
 
-Lead controllers see the complete effective definition roster and workers visible
-through their ownership boundary. Delegating workers see only allowed enabled
-leaf definitions and their visible workers. Unknown mailbox diagnostics remain
+The session-start instructions include the same complete definition metadata
+projection returned by `list` for that controller. It is a startup snapshot;
+use `list` for live agent state, ownership, or a refreshed definition roster
+after configuration changes. Leaf agents do not receive a definition roster.
+
+Lead controllers see the complete effective definition roster and agents visible
+through their ownership boundary. Delegating agents see only allowed enabled
+leaf definitions and their visible agents. Unknown mailbox diagnostics remain
 non-actionable.
 
 ## `inspect`
 
 ```json
-{ "action": "inspect", "worker": "implementer-1" }
+{ "action": "inspect", "agent": "implementer-1" }
 ```
 
-`inspect` accepts only `action` and the exact live worker label. It is available
-only to that worker's direct owner, and only when the worker is a current,
-unambiguous managed identity. The result is read-only and contains the exact
-session/pane identity, a bounded tail of the most recent 40 unwrapped terminal
-lines (at most 8 KiB), and advisory foreground process evidence when available.
-Its model-facing text includes the worker, session, pane, useful foreground
-commands, and recent activity; raw process and recent-output evidence remains
-in the structured result details.
+`inspect` accepts only `action` and the exact live agent label. It is available
+only to that agent's direct owner, and only when the agent is a current,
+unambiguous managed identity. The result is read-only live terminal/process
+evidence only: it contains the exact session/pane identity, Herdr's up to 80
+recent-unwrapped terminal lines, and advisory foreground process evidence when
+available. Herdsman applies a local 16 KiB byte cap to the captured terminal
+output. The public `recent_output_truncated` boolean is true only when that
+local byte cap truncates the output and false otherwise; process evidence has
+separate bounds. The result does not expose persisted Pi session-message
+history. Its model-facing text includes the agent, session, pane, useful
+foreground commands, and recent activity; raw process and recent-output
+evidence remains in the structured result details.
 The identity is checked again after capture; if the pane or Pi session was
-replaced, inspection fails closed. Inspection does not change worker state,
+replaced, inspection fails closed. Inspection does not change agent state,
 mailbox records, lifecycle, or available controls.
 
 ## `files` and `timeoutMs`
@@ -137,17 +153,26 @@ when the exact message limit permits. Otherwise they remain canonical references
 
 `timeoutMs` is valid on definition and session delegation and must be an integer
 from `5001` through `300000`. The startup budget reserves one bounded diagnostic
-window. Current message limits are governed by effective global/project/default
+window. Current message limits are governed by global/default
 settings and the fixed mailbox protocol ceiling. Managed mailbox records use
-protocol version 3, and control requests use the marker prefix
-`__PI_HERDSMAN_WORKER_V3__:`.
+protocol V4 in the `mailboxes-v4` namespace, and control requests use the marker prefix
+`__PI_HERDSMAN_AGENT_V4__:`.
+
+Do not attach or mention agent instruction files such as `AGENTS.md`, `CLAUDE.md`,
+`GEMINI.md`, or equivalents merely because they exist. Rely on normal project or
+runtime discovery. Attach one only when the task requires inspecting,
+modifying, comparing, or transmitting it, the user requests it, or its required
+instructions would not otherwise reach the target. Attach a required `SKILL.md`
+only when the task needs it and the selected definition does not already provide
+that skill. Ordinary relevant source, documentation, configuration, and
+evidence files remain attachable.
 
 ## `steer`
 
 ```json
 {
   "action": "steer",
-  "worker": "implementer-1",
+  "agent": "implementer-1",
   "message": "Also update the focused regression.",
   "files": [".pi-herdsman/review.md"]
 }
@@ -161,7 +186,7 @@ current assignment and does not create another final result.
 ```json
 {
   "action": "reply",
-  "worker": "implementer-1",
+  "agent": "implementer-1",
   "message": "Use option B."
 }
 ```
@@ -175,13 +200,13 @@ See [`ask_owner` API](ask-owner.md).
 ## `close`
 
 ```json
-{ "action": "close", "worker": "implementer-1" }
+{ "action": "close", "agent": "implementer-1" }
 ```
 
-Only `action` and `worker` are accepted. Close requires exact direct ownership,
+Only `action` and `agent` are accepted. Close requires exact direct ownership,
 or the lead-only evidence-backed orphan recovery condition. Closing abandons a
-pending owner question; closing a delegating worker cascades through directly
-owned workers first. Cleanup remains fail-closed when exact identity or ownership
+pending owner question; closing a delegating agent cascades through directly
+owned agents first. Cleanup remains fail-closed when exact identity or ownership
 cannot be proved.
 
 ## Result delivery and errors
@@ -189,13 +214,13 @@ cannot be proved.
 An accepted delegated task remains the internal mailbox `kind: "task"` request
 and has one correlated final result. Delivery goes to the exact owning Pi
 session and occurs exactly once. Model-visible completion wording uses
-`worker=<worker>`, `definition=<definition>`, `session=<id>`,
-`request=<id>`, and status. Details retain durable `workerLabel`,
+`agent=<agent>`, `definition=<definition>`, `session=<id>`,
+`request=<id>`, and status. Details retain durable `agentLabel`,
 `agentDefinition`, `piSessionId`, `piSessionFile`, result paths, elapsed time,
-context usage, truncation, and persistence-error evidence. The worker is cleaned
+context usage, truncation, and persistence-error evidence. The agent is cleaned
 up after the terminal result is delivered; the Pi session remains available for
 continuation.
 
 Tool failures return structured details for normal public errors. See
-[Errors](errors.md), [worker states](worker-states.md), and
-[workers and identity](../concepts/workers.md).
+[Errors](errors.md), [agent states](agent-states.md), and
+[agents and identity](../concepts/agents.md).

package/docs/reference/ask-owner.md

@@ -2,14 +2,14 @@
 
 [Documentation index](../README.md)
 
-`ask_owner` is mandatory managed-worker infrastructure for one direct-owner
+`ask_owner` is mandatory managed agent infrastructure for one direct-owner
 decision required to continue the current assignment.
 
 It is not a generic messaging channel.
 
 ## Availability
 
-Every valid managed worker receives the `ask_owner` tool at launch.
+Every valid managed agent receives the `ask_owner` tool at launch.
 
 Normal definition `tools`, `excludeTools`, and `noTools` policy cannot remove
 this infrastructure capability.
@@ -24,42 +24,42 @@ this infrastructure capability.
 ```
 
 `question` must contain non-whitespace text.
-`files` supplies supporting evidence using the same rules as `worker`: complete
+`files` supplies supporting evidence using the same rules as `agent`: complete
 strict UTF-8 text may be embedded, while other files are canonical local
-references and are not copied or snapshotted. Relative paths use the worker's
+references and are not copied or snapshotted. Relative paths use the agent's
 working directory. This does not weaken the sole-final-tool-call rule.
 
 ## Turn rule
 
 `ask_owner` must be:
 
-- the worker's only tool call in the turn;
+- the agent's only tool call in the turn;
 - the final tool call of the turn.
 
-The worker then stops and waits.
+The agent then stops and waits.
 
 A call made alongside another tool call is rejected.
 
 ## Eligibility
 
-A worker can ask only while it has a valid active assignment and:
+An agent can ask only while it has a valid active assignment and:
 
 - has no outstanding ask;
 - has no completed/final result pending;
 - has no pending state transition;
 - has no unacknowledged owner request;
-- has no ordinary unresolved direct-worker work.
+- has no ordinary unresolved direct-agent work.
 
-A delegation-enabled worker may ask its own owner when its unresolved direct
-workers are themselves validly blocked on owner questions. Ordinary active
-workers and pending worker results still block escalation.
+A delegation-enabled agent may ask its own owner when its unresolved direct
+agents are themselves validly blocked on owner questions. Ordinary active
+agents and pending agent results still block escalation.
 
 ## Durable effect
 
 On acceptance, Pi Herdsman creates one correlated ask record and sets
 `pendingAskId` while preserving the original active assignment request ID.
 
-The tool result tells the worker that the assignment is blocked and returns
+The tool result tells the agent that the assignment is blocked and returns
 details containing:
 
 ```text
@@ -67,7 +67,7 @@ askId
 assignmentRequestId
 ```
 
-The worker public state projects as `blocked` after the turn settles.
+The agent public state projects as `blocked` after the turn settles.
 
 Final assignment settlement is disabled while the ask remains pending.
 
@@ -76,20 +76,20 @@ Final assignment settlement is disabled while the ask remains pending.
 The exact direct owner receives the question through the existing owner-session
 delivery path.
 
-The system does not automatically forward a worker question through an ownership
+The system does not automatically forward an agent question through an ownership
 chain.
 
-If a delegating worker needs a lead decision, it independently calls `ask_owner`
+If a delegating agent needs a lead decision, it independently calls `ask_owner`
 on its own direct ownership edge.
 
 ## Reply
 
-The direct owner answers through the `worker` tool:
+The direct owner answers through the `agent` tool:
 
 ```json
 {
   "action": "reply",
-  "worker": "<exact worker>",
+  "agent": "<exact agent>",
   "message": "Use option B."
 }
 ```
@@ -101,13 +101,13 @@ The reply is correlated to:
 - run ID;
 - owner session;
 - workspace;
-- worker label;
+- agent label;
 - pane;
 - Pi session.
 
 A mismatched or stale reply fails closed.
 
-The worker clears the pending ask, acknowledges the reply request, and resumes
+The agent clears the pending ask, acknowledges the reply request, and resumes
 the same assignment with the owner answer.
 
 ## One outstanding question
@@ -116,18 +116,18 @@ Only one `ask_owner` question may be outstanding per assignment at a time.
 
 There is no ask timeout.
 
-The worker must not guess the owner answer and complete while blocked.
+The agent must not guess the owner answer and complete while blocked.
 
 Rejected calls identify the known eligibility reason, such as no active
 assignment, an existing owner question, settling state, a pending control
-request, or active direct-worker work.
+request, or active direct-agent work.
 
 ## Close
 
-Closing the worker abandons the pending question as part of worker teardown.
+Closing the agent abandons the pending question as part of agent teardown.
 
 ## See also
 
-- [`worker` `reply`](worker.md#reply)
+- [`agent` `reply`](agent.md#reply)
 - [Lifecycle](../concepts/lifecycle.md)
 - [Delegation](../concepts/delegation.md)

package/docs/reference/commands.md

@@ -1,29 +1,30 @@
-# `/workers` commands
+# `/agents` commands
 
 [Documentation index](../README.md)
 
-`/workers` is the human-facing worker-management command namespace.
+`/agents` is the human-facing agent-management command namespace.
 
-It is separate from the structured model-facing `worker` API.
+It is separate from the structured model-facing `agent` API.
 
 Commands require a lead Pi session with UI.
 
 ## Usage
 
 ```text
-/workers
-/workers agents
-/workers placement [tab|split]
-/workers stop
+/agents
+/agents definitions
+/agents placement [tab|split]
+/agents stop
 ```
 
 The plain command opens a native Pi selection menu with `Running`,
 `Definitions`, `Layout`, `Message limits`, and `Stop all…` destinations. The
-Message limits view edits the independent inline attachment and mailbox
-payload limits at global or trusted-project scope. It is available only to a
-lead Pi session with UI.
+Message limits view edits the independent global inline attachment and mailbox
+payload limits. It is available only to a lead Pi session with UI. Current
+values and presets show a rough token equivalent using four UTF-8 bytes per
+token. The enforced limits are bytes, not tokens.
 
-## `/workers agents`
+## `/agents definitions`
 
 Opens the native Definitions menu for the effective bundled, project, and
 global roster. Project definitions are included only when the trusted project
@@ -44,10 +45,10 @@ The details view can show:
 
 Bundled implementation paths are intentionally hidden from the human overview.
 
-Structured `worker list` keeps exact deterministic metadata, including exact
+Structured `agent list` keeps exact deterministic metadata, including exact
 source and skill paths when available.
 
-`/workers agents` does not probe runtime tool availability.
+`/agents definitions` does not probe runtime tool availability.
 
 Selecting a definition opens:
 
@@ -73,49 +74,53 @@ The command edits only the selected top-level `model`, `thinking`, or `enabled`
 line in the global Markdown override. It preserves unrelated frontmatter and
 the complete body.
 
+Details re-resolves the selected definition when opened, so it reflects current
+overlays and body references even if the menu remained open while configuration
+changed.
+
 Changes apply to future definition delegations and session continuations, not
-already-running workers or the lead Pi session.
+already-running agents or the lead Pi session.
 
 Standalone global definitions are editable too. Removing a field from one uses
 Pi's normal default; removing a field from a bundled override restores the
 bundled value.
 
-## `/workers` Running
+## `/agents` Running
 
 Select a live managed agent from the shared status projection to focus its pane.
 Pi Herdsman refreshes and verifies the exact label, pane, and session identity
-before issuing herdr's focus command. If the worker changed, no focus command
+before issuing herdr's focus command. If the agent changed, no focus command
 is sent.
 
-## `/workers placement`
+## `/agents placement`
 
 Selecting Layout opens a native selector showing the effective setting.
 Explicit values continue to set directly:
 
 ```text
-/workers placement tab
-/workers placement split
+/agents placement tab
+/agents placement split
 ```
 
 See [Configuration](configuration.md).
 
-## `/workers stop`
+## `/agents stop`
 
 Destructive lead-only emergency control.
 
 It aborts the current lead turn and attempts to close the exactly proven owned
-worker tree.
+agent tree.
 
 It reports discarded active work or durable pending results when present.
 
 Cleanup uses existing exact ownership proofs and proceeds conservatively across
 independent failures.
 
-Use ordinary `worker close` for normal targeted model-driven control.
+Use ordinary `agent close` for normal targeted model-driven control.
 
 ## See also
 
 - [`/chief` and chief mode](supervision.md)
-- [`worker` API](worker.md)
+- [`agent` API](agent.md)
 - [Configuration](configuration.md)
 - [Status widget](status-widget.md)

package/docs/reference/configuration.md

@@ -5,9 +5,9 @@
 Pi Herdsman intentionally has very little settings state.
 
 Agent behavior lives in Markdown definitions. The extension settings currently
-own worker placement.
+own agent placement.
 
-## Worker placement
+## Agent placement
 
 Settings shape:
 
@@ -32,12 +32,12 @@ Default:
 tab
 ```
 
-`tab` places future workers in the managed worker-tab workflow.
+`tab` places future agents in the managed agent-tab workflow.
 
-`split` places future workers by splitting from the caller's tab/pane placement
+`split` places future agents by splitting from the caller's tab/pane placement
 boundary.
 
-This affects future starts, not existing workers.
+This affects future starts, not existing agents.
 
 ## Message limits
 
@@ -56,13 +56,16 @@ Each accepts an integer from 1024 bytes (1 KiB) through 1048576 bytes (1 MiB)
 and defaults to 131072 bytes (128 KiB). The inline limit applies per file;
 eligible complete strict UTF-8 files are embedded in caller order only when
 the exact serialized mailbox record fits. Other files remain canonical
-references. The mailbox limit is the exact serialized `RequestRecord` or
-`AskRecord` admission size.
+references. The mailbox limit is the exact serialized `RequestRecord`,
+`AskRecord`, or text-only chief supervision record admission size. Chief
+supervision also has an existing fixed 8 KiB record ceiling, so its effective
+admission limit is the smaller of the configured mailbox limit and 8 KiB.
 
-Valid trusted project values override valid global values. Invalid values are
-ignored rather than clamped. Configure these values through `/workers` →
-`Message limits`; the fixed 1 MiB protocol safety ceiling remains in force for
-reading existing mailbox records.
+Only valid global values affect runtime behavior. Invalid global values are
+ignored rather than clamped, and project-local values for these two keys are
+inert. Configure the global values through `/agents` → `Message limits`; the
+fixed 1 MiB protocol safety ceiling remains in force for reading existing
+mailbox records.
 
 ## Settings scope
 
@@ -84,7 +87,7 @@ A project placement value is effective only when:
 
 If no valid trusted project placement is active, the global value is used.
 
-`/workers placement` opens a native selector showing the effective value and
+`/agents placement` opens a native selector showing the effective value and
 offering `tab` or `split`. Selecting a value writes to the current effective
 scope and verifies the value after writing; the confirmation reports whether
 that scope is `project` or `global`.
@@ -126,5 +129,5 @@ identity/restore behavior.
 
 ## See also
 
-- [`/workers` commands](commands.md)
+- [`/agents` commands](commands.md)
 - [Getting started](../getting-started.md)

package/docs/reference/errors.md

@@ -2,7 +2,7 @@
 
 [Documentation index](../README.md)
 
-Normal public `worker` failures use structured error details.
+Normal public `agent` failures use structured error details.
 
 ## Shape
 
@@ -38,12 +38,12 @@ must not be presented as exhausted cleanup.
 | Category                   | Meaning                                                                             |
 | -------------------------- | ----------------------------------------------------------------------------------- |
 | `not_running_inside_herdr` | Required herdr environment is missing.                                              |
-| `worker_label_exists`      | Requested/generated live label conflicts with an existing worker.                   |
-| `pane_not_ready`           | Worker pane/startup did not reach the required readiness boundary.                  |
+| `agent_label_exists`       | Requested/generated live label conflicts with an existing agent.                    |
+| `pane_not_ready`           | Agent pane/startup did not reach the required readiness boundary.                   |
 | `target_not_found`         | Exact requested identity or ownership evidence was not found.                       |
 | `target_ambiguous`         | More than one live candidate matched an identity that must be exact.                |
 | `rollback_failure`         | Primary operation failed and cleanup did not fully converge.                        |
-| `worker_busy`              | Worker state does not allow the requested control action.                           |
+| `agent_busy`               | Agent state does not allow the requested control action.                            |
 | `invalid_request`          | Request fields, values, definition input, file input, or preconditions are invalid. |
 | `internal_failure`         | An invariant or underlying operation failed outside a narrower public category.     |
 
@@ -58,7 +58,7 @@ Both are fail-closed behavior.
 
 ## Rollback
 
-When a worker launch fails, exact resources created by that attempt are cleaned
+When an agent launch fails, exact resources created by that attempt are cleaned
 only when ownership is proved.
 
 A `rollback_failure` can preserve:
@@ -84,4 +84,4 @@ This is output presentation behavior, not an error category.
 ## See also
 
 - [Recovery](../guides/recovery.md)
-- [`worker` API](worker.md)
+- [`agent` API](agent.md)