Synopsis
$ phrony agents publish MANIFESTDescription
Loads and resolves the manifest locally, then sends the resolved snapshot to the runtime over gRPC. The runtime stores an immutable agent version keyed by content hash and metadata.version.
Publishing does not make the version runnable. After publish, use deploy to activate the version for run.
MANIFEST is the path to a kind: Agent YAML file. For bundle manifests, use phrony bundles publish instead.
Manifest secrets
If the Agent declares a top-level secrets section, publish stores references only in the resolved manifest (fromEnv names). Publish does not read environment variables or send secret values.
Before running sessions for agents with secrets:
- Set
RUNTIME_SECRETS_ENCRYPTION_KEYon the runtime (see Environment variables). - At run time, supply the variables referenced in the manifest on the machine running
phrony run(export in the shell, use-e/--env-file, or passresolved_secretsfrom your backend)—seerunand Secrets.
What gets stored at publish:
| Store | Contents |
|---|---|
agent_versions.manifest | Resolved manifest with ref-only secrets (no API key values) |
The runtime records published_by from PHRONY_ACTOR (or the OS user when unset).
Example
$ phrony agents publish path/to/agent.yamlOn success, prints the agent reference and version:
demo/echo-agent 1.0.0Up next