Publish a flow to the marketplace

axiom flow publish promotes a compiled flow to the public marketplace from the command line — the same action the editor's Publish button performs. Once published, every Axiom tenant can discover the flow, fork it, and import it as a subflow inside their own flows.

You publish a compiled artifact, not a flow.yaml source file. So the two steps are always compile, then publish:

# Compile the flow.yaml in the current directory; prints the artifact id.
axiom flow compile
# → compiled flow artifact 01J8Z6K3W9XQ4M7C2YB5N0A1RT

# Publish that artifact to the public marketplace.
axiom flow publish 01J8Z6K3W9XQ4M7C2YB5N0A1RT

Prerequisites#

• A login session. Both axiom flow compile and axiom flow publish require axiom login; publishing without it prints Not logged in. Run "axiom login" first. and exits.
• A compiled artifact. Run axiom flow compile first and copy the artifact id it prints. Publishing takes that id as its only positional argument.

Publish a compiled artifact#

axiom flow publish 01J8Z6K3W9XQ4M7C2YB5N0A1RT

Because publishing is irreversible, the command prints a confirmation prompt and waits for y before doing anything:

  Publishing flow 01J8Z6K3W9XQ4M7C2YB5N0A1RT makes it publicly visible to every Axiom tenant.
  This cannot be undone — published flows are immutable.

  Publish? [y/N]

On confirmation it makes the flow publicly visible and prints:

✓ published flow 01J8Z6K3W9XQ4M7C2YB5N0A1RT
  visibility: public — marketplace-visible, forkable, importable as a subflow
  this version is immutable; compile a new flow to iterate further

A published artifact can never be edited or unpublished. To change a published flow, edit its flow.yaml, run axiom flow compile again to get a new artifact id, and publish that.

Publish without the prompt (CI and scripts)#

Pass --yes (-y) to skip the confirmation — required when stdin is not a terminal, or the command blocks waiting for input:

axiom flow publish 01J8Z6K3W9XQ4M7C2YB5N0A1RT --yes

Add --json to emit a single machine-readable object instead of the human lines, so a script (or an agent) can confirm the result programmatically:

axiom flow publish 01J8Z6K3W9XQ4M7C2YB5N0A1RT --yes --json

{
  "artifact_id": "01J8Z6K3W9XQ4M7C2YB5N0A1RT",
  "visibility": "public"
}

The flow CLI lifecycle#

axiom flow publish is the last verb in the command-line flow lifecycle. The full set of axiom flow verbs takes a flow from an empty file to a public artifact without ever opening the canvas:

A typical command-line session runs them in order:

axiom flow new greeter                 # write greeter.flow.yaml
axiom flow validate greeter.flow.yaml  # local sanity check
axiom flow compile greeter.flow.yaml   # → artifact id
axiom flow run 01J8Z6… -d '{"name":"Ada"}'   # try it
axiom flow publish 01J8Z6…             # share it

CLI and editor publish are the same action#

axiom flow publish and the editor's Publish dialog are the same action — both promote the artifact to the same public marketplace listing with the same final visibility. Publishing from the CLI and publishing from the canvas produce an identical marketplace listing; use whichever surface you are already in.

With this verb, all three Axiom artifact types now have full command-line ↔ UI parity for both creating and publishing:

• Nodes/packages — axiom push then axiom publish <package>@<version>, or the console.
• Flows — axiom flow compile then axiom flow publish <artifact-id>, or the editor's Publish button.

Next steps#

• Run your first flow — build a flow.yaml and run it before you publish.
• Nodes, packages, and flows — how a published flow becomes an importable subflow.
• Author packages and flows with Claude Code — drive this whole lifecycle from an AI agent.