stax push

Push a built artifact from the local artifact directory to an OCI-compatible registry. Once pushed, the artifact is available to anyone with registry access for pulling, materializing, or inspecting.

Usage

stax push ghcr.io/myorg/agents/backend-engineer:3.1.0

How pushing works

1. The CLI locates the built artifact in .stax/artifacts/
2. Each layer is uploaded to the registry as a content-addressed blob
3. The OCI manifest is pushed with the specified tag
4. The registry returns the manifest digest for verification

Because layers are content-addressed, pushing a new version of an agent only uploads layers that actually changed — unchanged layers are deduplicated by the registry.

Tagging strategy

The reference after push determines the repository and tag:

# Push with a semver tag
stax push ghcr.io/myorg/agents/backend-engineer:3.1.0

# Push with a branch or environment tag
stax push ghcr.io/myorg/agents/backend-engineer:staging

# Push with a latest tag
stax push ghcr.io/myorg/agents/backend-engineer:latest

The current reference CLI pushes the single artifact present in .stax/artifacts/. Multi-persona publishing workflows are future work.

Authentication

You must be authenticated with the target registry before pushing. See stax login.

Example output

Pushed ghcr.io/myorg/agents/backend-engineer:3.1.0
  digest: sha256:a3f8c1…e7d2

Related commands

• stax build — Build the artifact before pushing
• stax pull — Pull an artifact from a registry
• stax login — Authenticate with a registry