The local target runs directly on the host with SQLite, local blob storage, and loopback-only content origins. The loopback application gives the local owner browser access without a sign-in form. The source installation requires Node.js 24.12 or newer and pnpm 10.34.3.
Run the packaged release
Artifact Server v0.1.2 includes a portable Node.js package. It requires Node.js 24.12 or newer.
Download and verify the package
Download these files from the v0.1.2 GitHub release:
artifact-server-0.1.2-node.tar.gzartifact-server-0.1.2-node.tar.gz.manifest.json
Run this command in the download directory:
node -e 'const crypto = require("node:crypto"); const fs = require("node:fs"); const archive = process.argv[1]; const manifest = JSON.parse(fs.readFileSync(process.argv[2], "utf8")); const actual = crypto.createHash("sha256").update(fs.readFileSync(archive)).digest("hex"); if (actual !== manifest.sha256) throw new Error("Archive checksum mismatch"); console.log(actual);' artifact-server-0.1.2-node.tar.gz artifact-server-0.1.2-node.tar.gz.manifest.jsonFor provenance verification, use the supply-chain guide.
Extract and start Artifact Server
tar -xzf artifact-server-0.1.2-node.tar.gz
./artifactserver/bin/artifactserver openOpen the printed URL. The application stores its data in .artifact-server by default.
Run from source
Install dependencies
git clone https://github.com/plannotator/artifact-server.git
cd artifact-server
pnpm installStart Artifact Server
pnpm devOpen the printed URL. pnpm dev starts both the web application and API. Do not run artifactserver open as a second setup step. Run CLI commands from the checkout with pnpm artifactserver <command>.
Publish from an agent
Connect the agent to the running development installation:
pnpm artifactserver connect --data .artifact-serverThen install the Artifact Server skill:
npx skills add plannotator/artifact-serverThen ask the agent to upload the finished file. In clients that expose skills as slash commands:
/artifact-server upload that HTML design docThe agent returns the full-screen review link first.
Local access behavior
Requests from the loopback application origin can obtain the local-owner session without a sign-in form. Remote access still requires authentication. Hosted and private-team deployments use their selected identity provider.