Updates

Folder shares (static sites) can now use WebAssembly and workers. Load an in-browser analytics engine such as DuckDB-WASM from jsDelivr and query Parquet or other data files bundled in the folder with SQL, right in the page. You can share an interactive data dashboard without running a server.

As a sample, we published a dashboard of 150 years of monthly records from 158 Japan Meteorological Agency stations (200,000 rows). Every time you move the year, a SQL query runs in your browser. The live sample and its source code are in artifactshare/examples.

File owners can now choose how many versions each file keeps. For files that gain a version on every run, such as a dashboard updated on a schedule, older versions are deleted automatically and their storage is released.

In the CLI, artifactshare edit <file> --retain-versions 24 keeps only the latest 24 versions. --retain-versions all removes the limit and keeps every version again.

Free workspaces can now choose link sharing for each file. Anyone with the share link can view the file without signing in to Artifact Share. Expiration works the same as on Plus: new workspaces default to 30 days with no maximum. Existing workspaces keep their saved expiration settings, and changing plans does not rewrite them.

In the browser, choose "Anyone with the link" in the who-can-view dialog. In the CLI, pass --visibility link; in MCP, set visibility to link.

Collaborators can now add a new version at the same URL instead of asking the file's owner to update it. This applies to workspace members when a file is shared with its workspace or project. When the file's workspace allows uploads from external members, someone whose email address was added directly can also update it after signing in with Google or Microsoft.

In the browser, add a version from the version control in the lower-right corner of the file. In the CLI, use the same artifactshare update command as before.

You can now read the HTML or Markdown an agent wrote in your own browser before sharing it. Say "preview it with as" and the file is served locally, looking the way it will once published.

To ask for a change, select the element or the text and leave a comment on it. Submitting a batch hands those comments to the agent, which reports back on each one as it fixes them. The page reloads whenever the file is saved, so you see the result in place.

Until now this meant a round trip: look in the browser, then put what you noticed into words in the terminal. Pointing at the place you mean removes that step.

Comments are stored locally and survive closing the preview. Nothing is uploaded. Sharing happens only when you choose it from the page.

The source code for Artifact Share is now available on GitHub. You may study and modify the code and self-host it for your organization.

The repository is source-available, not OSI-approved open source. See the repository license for its terms, including the restriction on offering a directly competing hosted service.

You can follow the development of the web service, CLI, and documentation in the public repository. We will continue publishing fixes and improvements there.

Artifact Share CLI 0.11.0 adds a login preset for AI agents. Run npm exec --yes --package=@artifactshare/cli -- artifactshare login --preset agent and choose one project in your browser to create a CLI session limited to that project.

Settings → Tokens now lists active Artifact Share CLI login sessions. You can revoke one session or revoke them all at once.

Teams post files to a shared project but only the people who go check the project notice new work. Sharing a link manually in Slack every time is easy to forget.

A project can now be linked to one Slack channel. Start from Project detail → "…" menu → "Slack notification", and pick the channel on Slack's own authorization screen. Any channel you belong to works, including private ones. When a new file is posted to a linked project, the channel gets an automatic message with the title, uploader, and link. Multiple uploads posted in a short window are combined into a single message.

Artifact Share CLI 0.8.2’s artifactshare append <target> <path> and remote MCP’s append_artifact append content to a single shared file and create a new version at the same share link. For Markdown, they append to the end of the current source. For HTML, they append immediately before the closing body tag when present, or at the end otherwise. Neither adds a newline or separator.

If another update lands first, the operation preserves it and returns version_conflict with the current version ID. Run the operation again to append to the latest version. Static sites are not supported. To replace the full source, use CLI update or MCP update_artifact.

When people use a mobile development environment and an agent while travelling, they can carry a design document forward and continue the work on a PC later. Setting user-level home_audience to private keeps that in-progress document from being unintentionally shared with everyone in the workspace in this CLI environment, without requiring the who can view to be specified every time.

The new CLI reference explains how to share, update, read, comment on, and organize files from a terminal. It also documents JSON output, settings, destinations, and recovery paths so people and agents can find the right command quickly.

When no destination is specified, share posts to home; use user-level home_audience as the personal safe default, confirm its effective value, and use repository scope only for a policy agreed by all participants.

This page is new. Recent improvements to Artifact Share are now announced here, with labels showing whether a change affects the web app, the CLI, AI agent integrations, or MCP.

The CLI also ships its own changelog now: run artifactshare changelog to see what changed in your installed version.

Upload a folder that contains HTML with Mermaid code blocks and Artifact Share renders the diagrams in the shared site view.