Artifact Share CLI
Artifact Share CLI: an agent publishes HTML, Markdown and static sites at a stable link and updates it with new versions
- 35 ★ on the repository
- Last commit
Extended access
Why this level
- Files go to the service's servers, and a link-access file opens for anyone who holds the link
- The delete command removes a published file permanently
Install
- Works in
Manual install
npm exec --yes --package=@artifactshare/cli -- artifactshare share ./report.htmlThe command from the README; the first run prints a sign-in link. The agent skill is installed by artifactshare init.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Files go to the service's servers, and a link-access file opens for anyone who holds the link
- The delete command removes a published file permanently
This is third-party code. Review the repository files before installing.
What it does
Artifact Share stores finished files an agent has made: HTML reports, Markdown documents, folders and exported sites. The official @artifactshare/cli sends a file or folder to the service and prints a link. The update command adds a new version at the same address, append adds a fragment to the end of a document, and share with a key updates one file across repeat runs in CI or on a schedule. Access is set at publication or with the edit command: private, workspace, project, listed email addresses, or a link with an expiry. The comments commands read and write comments on a published file, download saves a file or a whole site locally, and preview shows a file in the browser for edits before publishing and uploads nothing. The init command detects Claude Code, Codex or Cursor and installs a bundled skill with the CLI guide. A remote MCP server at https://artifactshare.com/mcp does the same work. Every command accepts a --json flag with a stable response contract.
Who it is for. Teams whose agents assemble reports and prototypes and whose colleagues and clients need a link instead of a chat attachment.
Good fit when
- The agent built a weekly HTML report and a manager has to open it by link
- A DuckDB-WASM dashboard goes out as a static site from the dist folder
- A daily CI run refreshes the same report by key instead of creating new links
- A client leaves comments on a published page and the agent reads them with comments list
- A Markdown draft is checked in the browser through preview before it reaches shared access
Not a fit when
- The file contains secrets or personal data: the service stores it on its servers
- You want to self-host for a competing cloud service: the repository license forbids that
- You only need to share source code: the service is built for finished HTML, Markdown and static sites
- An environment with Node.js older than version 22 and no npm access
Example request
Publish ./report.html and give me the link, with access for my workspace only.Limitations
The repository is open to read, but its license restricts offering Artifact Share as a competing cloud service and is not OSI-approved. The npm package through version 0.9.0 stays under Apache-2.0. Node.js 22 or newer is required, and CI uses an ARTIFACTSHARE_TOKEN. Without a token a non-interactive run fails with auth_required and does not wait for sign-in. Publications are stored on the service side.
How to disable. Delete published files with the artifactshare delete command, then sign out with logout. The bundled skill is removed by skills remove. For the MCP connection, revoke access in the client settings.
FAQ
How do I publish a file through Artifact Share?
Run npm exec --yes --package=@artifactshare/cli -- artifactshare share ./report.html. On the first run the CLI prints a sign-in link, and after sign-in the published file's address appears.
How do I update a file without changing the link?
The update command with the address or id and a path to the new file adds a version at the same address. For repeat jobs run share with a key: the first run creates the file and later runs add versions.
How do I work in CI without a browser?
Issue a token at artifactshare.com/settings/tokens and pass it in ARTIFACTSHARE_TOKEN or with --token. Without a token a non-interactive run fails with auth_required.
Can I read comments from a published page?
Yes, comments list shows them, and post, resolve and reopen write and close them. The output comes as JSON, so the agent parses it without screen text.
How is Artifact Share different from Claude Artifacts?
Claude Artifacts builds a page inside the chat. Artifact Share publishes the agent's finished files at a stable link with versions, comments and access rules.
Discussion
No questions or reviews yet.
Related
CLI toolsA plugin with a CLI and skills for Claude Code and Codex: agent-made HTML goes to a private AWS archive readable from a phone.
A CLI and skill for an agent to publish reports and specs as HTML documents that a team comments on, with every version kept
The fl CLI puts a folder of Markdown and HTML online as a site in one command and returns the URL and a claim link to an agent.
Pagecast CLI, skill and MCP server that publish HTML reports, Markdown and static sites to Cloudflare Pages behind a short link
A skill, an MCP server and a CLI turn Markdown from an agent into a short link to a web page that opens without signing in.
An Overleaf CLI that pulls LaTeX projects to a folder, pushes edits, compiles PDFs and exposes them to an agent through MCP
README in short
The repository README covers the monorepo layout, local development and contribution through proposals without code. The command reference lives in the CLI package README, and the agent guide ships as a bundled skill.