openartifacts ยท diff
git:20260904.3be008f to git:20260904.b2ad8c0
8 added, 1 removed. Audit A to A.
---
name: openartifacts
description: Publish, update, list, fetch, or unshare public OpenArtifacts documents and manage this machine's OpenArtifacts access.
+ metadata:
+ hermes:
+ category: productivity
+ tags: [publishing, markdown, artifacts]
---
# OpenArtifacts
- Use the `openartifacts` CLI for every operation. Do not read OpenArtifacts config files, look for credentials, or print `OPENARTIFACTS_TOKEN`.
+ Use `openartifacts` as the command prefix when it is installed. Otherwise use
+ `npx --yes openartifacts@latest`; do not require another package install first.
+ Do not read OpenArtifacts config files, look for credentials, or print
+ `OPENARTIFACTS_TOKEN`.
- Publish Markdown or HTML: `openartifacts publish <file>`
- List documents: `openartifacts list`
- Fetch current HTML: `openartifacts get <docId>`
- Withdraw a document: `openartifacts unshare <docId>`
- List machine tokens: `openartifacts tokens`
- Revoke one: `openartifacts revoke <tokenId>`
- Sign in again after an `unauthorized` response: `openartifacts login`
The first authenticated command may wait for approval. Relay both sign-in URLs and the user code printed by the CLI, then keep waiting; never ask the user to copy a token. Return the public URL printed by `publish`.
Publishing the same local file again updates its existing document. If an update returns `not_found`, stop and report it; do not create a replacement.
Markdown files use ordinary Markdown rendering. Obsidian wikilinks, embeds, and callouts are not expanded and will appear as literal text.
If the user explicitly wants a new link after an update returns `not_found`, ask for confirmation, run `openartifacts unshare <oldDocId>` to forget the stale local mapping, then publish the file again. Never take that recovery path automatically.
If publishing returns `quota_exceeded`, show the error and advise the user to wait for the current quota window or remove an unused document, as appropriate. Do not blindly retry. If publishing returns `limit_reached`, show its limit and upgrade link when present, and retry only after the user confirms the limit was changed.