Skip to content

Latest commit

 

History

History
45 lines (30 loc) · 1.59 KB

File metadata and controls

45 lines (30 loc) · 1.59 KB

Command-line interface

Agents normally publish through the Artifact Server Skill or MCP. Use the CLI when you want to publish directly or run operator commands from a terminal.

A packaged release will provide the artifactserver command. Its download, verification, and PATH setup commands will be added on release day. Until then, run the examples from a source checkout by replacing artifactserver with pnpm artifactserver.

Publish an artifact

Publish one finished file or a complete directory:

artifactserver publish ./report.pdf
artifactserver publish ./dist --public --name "Product prototype" --tag prototype

Publication returns JSON with three browser links:

Link Purpose
links.review Opens the exact version full screen with comments. Share this link first.
links.artifact Opens the stable link that follows the current version.
links.version Opens the immutable raw version without the Artifact Server interface.

Use a remote server

Sign in once, save a named profile, and use it when publishing:

artifactserver auth login https://artifacts.example.com --name team
artifactserver publish ./dist --profile team

Publish another version

Provide the artifact ID and expected current version:

artifactserver publish ./dist \
  --artifact art_example \
  --expected-version ver_example

The expected version prevents an old client from replacing a newer current pointer.

Run artifactserver --help or artifactserver <command> --help for the complete command reference.