protoagent.plugin.yaml

id: delegates
name: Delegate Registry
version: 0.1.0
description: >-
  A unified, hot-swappable registry of the agents and endpoints your agent can
  talk to — fleet A2A agents, OpenAI-compatible model endpoints, and ACP coding
  agents — behind one `delegate_to(target, query)` tool. Manage them in config
  (and, from PR2/PR3, a console panel) without a restart. See ADR 0025 and
  docs/guides/delegates.md.

  Declare delegates in a top-level `delegates:` list (a list, ORBIS-style — not a
  plugin config section). A built-in (always-on, can't be disabled) — it
  contributes the `delegate_to` tool ONLY once you declare at least one delegate,
  so it's a no-op until then. Manage the roster in Workspace settings ▸ Delegates.

  Example (langgraph-config.yaml):
    delegates:
      - name: helm
        type: a2a
        description: Chief of staff — planning, fleet coordination.
        url: https://helm.example/a2a
        auth: { scheme: bearer }        # token in secrets.yaml / *_env
      - name: opus
        type: openai
        description: Heavy reasoning model.
        url: https://api.proto-labs.ai/v1
        model: protolabs/reasoning
      - name: proto
        type: acp
        description: Terminal coding agent for this repo.
        command: proto
        args: ["--acp"]
        workdir: ~/dev/my-repo
        permissions: allowlist
# Always-on (ADR 0025): the registry is core runtime infrastructure, not an
# optional add-on — `builtin: true` makes it load unconditionally (it can't be
# disabled and is hidden from the Plugins management list). It still stays a no-op
# until a delegate is declared (register() adds `delegate_to` only when the roster
# is non-empty). So the gate is "did you declare a delegate", never a plugin toggle.
builtin: true

# Declarative only (not yet enforced) — surfaced in the console for transparency.
capabilities:
  network: ["*"]            # reaches the configured agents/endpoints
  filesystem: workdir       # acp delegates do local I/O in their workdir