oz0 job save-as-flow
For: Operators and developers looking up a command.
Turn a job that worked into a draft flow in your workspace draft of a plugin: each tool call that succeeded becomes a tool step with its recorded arguments, and each child agent job an agent step.
Values the job was given become the flow's inputs (its input_schema, which holds their names and types, never their values); values an earlier step returned become references to that step (${{ steps.<id>.<field> }}); text the model wrote becomes an agent step that writes it again at each run; every other value is kept and listed for you to review. One job shows one path, so the draft has no conditions.
Values of these shapes are never kept: email addresses, phone numbers, IBANs, payment card numbers, Swedish personal numbers, IP addresses, the tenant's secrets, and text written like a flow expression (${{ }}), including such map keys; they become inputs and are flagged. Names, street addresses and other free text are not recognised, so review every kept value.
For a job about a data subject, every text and number becomes an input, and so does every map with a key other than a lowercase field name such as order_id. The manifest gets the flow and a flow tool for it (tools: [{id, flow}]); list the tool in an agent's tools to offer it. Nothing is a revision until you save one in the studio or with oz0 workspace save.
The draft becomes plugin source, which every reader of the workspace reads: look at it with --preview first, then write it with --confirm-shared. A job about a data subject needs --confirm-subject, and a chat's turn is never saved. The tenant's admins with the content permission may; it is audited. --dir writes into a plugin folder on disk instead.
Usage
oz0 job save-as-flow JOB --into PLUGIN [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--confirm-shared | bool | you know the draft becomes plugin source that every reader of the workspace reads (required to write it) | |
--confirm-subject | bool | save a data subject's job: you looked at the draft and what it lifted | |
--dir | string | write into this plugin folder on disk instead of your workspace draft | |
--into | string | the plugin (workspace folder) the flow goes into (required) | |
--name | string | <agent>-flow | the flow's name |
--preview | bool | only show the draft; nothing is written | |
--tenant | string | default | tenant |
--tool | string | <plugin>_flows, or the first free <plugin>_flows_N | the flow tool's ID |
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.