oz0 plugin eject
For: Operators and developers looking up a command.
Write the full folder of a plugin that is one part on its own (an agent in one file, a flow file or a skill, with no oz0-plugin.yaml), for when it needs code of its own, evals or more parts: oz0-plugin.yaml with the generated manifest's name, kind and uses:, agents/<name>.yaml with the agent's fields as written (addresses kept) and instructions: prompts/<name>.md, the prompt with the file's body, and evals/<name>.yaml with one case to fill in; a flow goes to flows/ with its evals, a skill to skills/<name>/.
The plugin keeps its name and its version, so installing the folder over the installed plugin updates it and its versions and rollouts go on: the version is --version, else the installed plugin's when your CLI context's server has it, else the generated one. Change version: in oz0-plugin.yaml when you release a new one. It writes into --out (default: a folder of the plugin's name here) and refuses one that has files.
Usage
oz0 plugin eject <file.md | folder> [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--out | string | the folder to write (default: a folder of the plugin's name in the current folder); it must be empty or new | |
--tenant | string | default | the tenant whose installed plugin's version eject keeps |
--version | string | the installed plugin's, else the generated one | the manifest's version |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.