Agentflow Plugins

Plugins package reusable team workflows and CLI tools for supervised Agentflow runs. They resolve from Git or local folders, pin through agentflow.plugins.lock.json, and compile into normal Agentflow runtime behavior.

Must Know

• Prefer native repo/device CLIs for simple one-tool work that agents can discover with --help.
• Prefer a plugin when the capability composes multiple CLIs, normalizes fragile sequences, needs credential isolation, needs stable JSON I/O, or should be reused across graphs.
• Tool --help is the agent-facing API contract.
• Tool implementation can be shell-native or language-backed; choose based on complexity, parsing needs, tests, dependencies, and portability.
• Name plugins by domain/capability, and name exports narrowly enough to avoid collisions with native CLIs, reserved runtime commands, and other plugin tools.
• Secrets belong in plugin credential scopes and agentflow auth, never inline graph config.
• Plugin workflows publish stable public artifacts from one publish_node; consumers should not depend on generated internal node ids.
• A plugin is not complete until it resolves and validates from a consumer graph.

Route By Task

• Need workflow plugin layout, manifests, plugin_file, plugin://, config, lockfiles, or public artifacts: read references/plugin-workflows.md.
• Need graph primitives, supervision, delivery, or run behavior: use agentflow.