Updates

The share page URL now stays in sync with the # (URL fragment) of the content inside it. If a page keeps its state in the fragment, such as a slide number or a dashboard's tab and filters, the share page URL reflects what you are looking at. Send that URL and the recipient opens the same view.

For example, opening /a/<id>#/3 starts a slide deck on slide 3. Narrowing a dashboard by date or channel changes the URL to something like #from=2026-07-01&media=video. Copy link includes the current fragment too.

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.

Opening a shared file without permission no longer leaves you at a dead end. Send an access request from that page. The request goes to someone who can approve it, such as the file owner.

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.

Home now shows files you created but have not opened yet above Recently seen. This includes files created through the web app, CLI, or an agent using your account.

Opening a file removes it from this section. It then appears in Recently seen, so both lists keep a clear purpose.

The same order is used on desktop and mobile. When more files are waiting, you can continue to the existing My files page.

On the shared page, "Who viewed" now includes signed-in people the file or project was shared with, alongside internal members. Open it from the viewer count next to the view counter, or from "Who viewed" in the "…" menu.

• External recipients with an explicit file or project share are included and can see other recipients of the same file. People who only have the link are not included.
• Viewing history from before this feature became available is also shown.
• Entries record that a file was opened; they are not read receipts.

When you return to a file while signed in, its shared page now shows version updates and new comments since your previous visit. Select the version update to open version history, or select the new comment count to open the comments panel.

From version history, you can open any published previous version of an HTML page, Markdown document, or static site and see its contents at that point in time. A notice remains visible while you are viewing a previous version, so you can return to the current version at any time. The selected version is preserved when you reload the page or use your browser's back and forward buttons.

To compare it with the current version, open the previous version link in another browser tab or window.

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.

Recently seen on Home now places dates in a compact rail beside each row. You can keep the viewing date as a memory cue while seeing more files at once.

Long titles are shortened to one line, and files viewed on the same day stay aligned without repeating the date. The full Recently seen page keeps its existing date headings.

Date labels include the weekday, and the row gives more room to file titles on wider screens.

The new Markdown viewer is now the default for every workspace. Shared Markdown opens as a focused article with a responsive table of contents, compact frontmatter, and typography designed for longer technical documents.

Code blocks use syntax highlighting and a dark, copyable frame. Wide tables scroll horizontally, long URLs wrap on smaller screens, standalone YouTube links become privacy-enhanced embeds, and Mermaid diagrams load only when a document needs them. Disclosure blocks written with <details> and <summary> are also supported.

Existing share links and version history stay the same. Comments continue to follow the document when their text can be matched after rendering; a comment may move slightly when the new layout changes line wrapping.

Explore the Markdown viewer demo to try the table of contents, code highlighting, Mermaid, YouTube, responsive tables, and disclosure blocks in one document.

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.

We removed the global Recent activity section from Home to focus the page on Recently seen, My files, and Projects. Project-specific activity history remains available.

Unread comment counts now include only comments you can actually view, excluding inaccessible or deleted comments and hiding the count when it is zero. Opening an updated file clears its unread version-update indicator, while comments remain unread until they are shown in the comment panel. Returning to the list reflects each state correctly.

We fixed Home rows overflowing into the sidebar and removed hover previews only from the My files sidebar on Home, while retaining them in wider lists. Visibility chips now use the shorter labels Specific, Project, Company, and Link sharing. Permissions and recipients are unchanged.

Official YouTube videos embedded in shared HTML, Markdown, and static sites can now play directly in Viewer, including in fullscreen. Production records and explanatory material can show videos in context instead of separating them into external links.

Only official embed iframes from https://www.youtube.com and https://www.youtube-nocookie.com are allowed. Other external iframes remain blocked. The Permissions Policy delegates fullscreen only to self and these two origins; no other browser permissions are expanded.

This change does not add a new embedding interface or custom Markdown syntax. It enables official iframes that authors already include in their shared pages.

Files can now be downloaded from links and buttons in HTML or static sites displayed in Artifact Share Viewer. This fixes downloads such as data URI links using <a download> that the Viewer sandbox previously blocked. Authors can share a download page, and viewers can download its files using the controls already built into the page. This change does not add a new download button to Viewer.

Links using cursor:, vscode:, codex:, claude:, or claude-cli: in shared HTML, Markdown, and static sites can now open their corresponding apps from Artifact Share Viewer. A shared file can lead to Cursor MCP settings, files or settings in VS Code, or a new task in Codex, Claude, or Claude Code. Nothing launches automatically: the Viewer requires a real click on an existing link, followed by the browser's confirmation. This change does not add a new Viewer button, and URL schemes outside the allowlist remain blocked.

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.

Home now has two tabs, My files and Recently seen. Recently seen lists your own uploads together with other people's files you opened through a share link, ordered by when you last viewed each one, and leaves out anything you no longer have access to. You can search the list by file name, title, project, or owner, and page through 20 items at a time to reach your full history. This makes it easier to get back to a file you opened once through a share link, including ones shared deep in a chat or message thread.

Artifact Share now uses Google Analytics 4 to see how people move from viewing a shared file, through signing in and creating a workspace, to posting a first file. This helps us find where visitors drop off. The privacy policy has been updated to describe this in full.

App connections and CLI sign-in now make the connecting app, requested access, and approval code easier to verify. On mobile, file lists and activity history keep important details such as owners, actors, and update times visible. When storage approaches its limit, Artifact Share shows the remaining capacity and the next action to take. Guides, About, the landing page, and settings also provide clearer paths to the relevant next step.

When you start a browser upload while signed out, the sign-in page now explains that you are signing in to upload and puts Google and Microsoft first. After signing in with either provider, the upload screen opens as planned.

People who first encounter Artifact Share through a shared file can now learn what the product is without leaving the viewer. Focusing or hovering over the information icon shows a brief product overview. The preview is for viewing only, with no links or buttons. The icon itself links to About: click, press Enter, or tap it to continue. From About, the main call to action leads to Getting Started.

The Free plan on the pricing page now links to a new getting started page. No credit card is required, and you do not need a project for your first post.

The workspace settings screens have been redesigned. Wider layouts let tables display without horizontal scrolling, and a new General page brings together workspace name editing and role permissions.

The Home, Recently Viewed, Projects, and Project Detail list pages now use more of the available width. The name column takes up the remaining space, so long file names no longer get cut off.

Team workspace admins can now review every project and file in the workspace from Settings, with metadata such as owner, who can view, and storage size.

Workspace settings now has an Activity page, and the billing page shows an estimate of this month's charge up front.

Workspaces can now share day-to-day operations among multiple admins while keeping one owner responsible for billing and role assignments.

Public pricing pages are now available in Japanese and English. Workspace owners can choose Plus or Team, monthly or yearly billing, and JPY or USD from billing settings, then continue to Checkout.

Plan prices do not vary by contributor count. Plus includes 10 GB of storage, and Team includes 100 GB. Active subscriptions can continue beyond the included storage for ¥16 per GB-month or $0.10 per GB-month.

Workspace admins can now complete offboarding entirely from the settings page.

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.

The signed-in home page now shows a short list of recent uploads and updates across your workspace.

Use it to jump back to files you or teammates touched in the last few days.

Shared file links now include Open Graph images and descriptions when pasted into chat apps or social feeds.

No action is required for existing links. New shares pick up the preview automatically.

Refreshing a file page in the same browser session no longer adds a second view to the total.

View counts still update when someone opens a link from a new device or browser profile.