Artifacts

Radius artifacts turn an HTML page, Markdown document, Mermaid diagram, CSV table, JSON or JSON Lines document, asciinema terminal recording, or small static site into a link you can share. They are useful for reports, dashboards, previews, demos, and other output that is easier to view in a browser.

Each artifact has a Radius viewer page with its title, visibility, expiry, and revision history. Share this viewer URL rather than the underlying site URL.

Install Radius API access

Artifact publishing is provided by the radius-api skill in the published Radius extension package:

pi install npm:@earendil-works/pi-radius

Restart Pi or run /reload, then authenticate with /login radius. Artifacts are stored in the organization selected during login.

Publish an artifact

Ask Pi to publish a single HTML, Markdown, Mermaid, CSV, JSON, JSONL, or asciinema file, or a directory:

Publish report.html as a Radius artifact titled "Deploy report".
Publish notes.md as a Radius artifact titled "Release notes".
Publish architecture.mmd as a Radius artifact titled "System architecture".
Publish results.csv as a Radius artifact titled "Benchmark results".
Publish events.jsonl as a Radius artifact titled "Run events".
Publish demo.cast as a Radius artifact titled "Pi demo".

Publish the static site in ./report as a Radius artifact titled "Q3 dashboard".

A directory must contain a supported index.* entry point at its root. It can also contain relative CSS, JavaScript, images, and other assets. Pi uploads the files and returns the artifact's Radius viewer URL.

Artifacts are private to your organization by default, so viewers must sign in to Radius. If anyone with the link should be able to view one, explicitly ask Pi to publish it publicly. Do not make an artifact public if it contains private or sensitive information.

Note that two-step verification requirements can take a while to take effect. When an organization requires two-step verification, Radius can delay enforcing it for up to 12 hours for existing grants on some resources.

Update an artifact

Publishing changes creates a new revision instead of replacing the history. Ask Pi to publish the same directory again:

Publish the updated ./report directory as a new revision of its Radius artifact.

Keep the artifact ID or viewer URL if you want to update it from another session. A new directory revision inherits unchanged files from the previous revision; Pi uploads the files that changed and removes inherited paths that should no longer exist.

Previous revisions remain available from the revision selector on the viewer page. Publishing a revision also refreshes the artifact's expiry.

View and manage artifacts

Open Your organizations, select the organization, and choose Artifacts. From there you can:

Open an artifact and browse its revisions
Change its visibility between private and public
See its size, expiry, and last update time
Set an artifact-specific lifetime
Delete the artifact and all of its revisions

Members can see and manage artifacts they uploaded. Organization owners and admins can see and manage artifacts from every member.

You can also ask Pi to list, inspect, or delete artifacts:

List my Radius artifacts.
Show the revisions for artifact <id>.
Delete Radius artifact <id>.

Artifacts expire after the organization’s configured default lifetime (30 days by default), refreshed on every publish. Organization owners and admins can set a maximum lifetime up to 365 days and change the default from the organization’s Artifacts page. An artifact can also use its own lifetime override. Deleting an artifact removes every revision.

Supported formats

Agents can upload various files, but some are specially handled for better display:

Format	Single-file extensions	Directory entry point
HTML	`.html`, `.htm`	`index.html`
Markdown	`.md`, `.markdown`	`index.md`
Mermaid	`.mmd`, `.mermaid`	`index.mmd`, `index.mermaid`
CSV	`.csv`	`index.csv`
JSON	`.json`	`index.json`
JSON Lines	`.jsonl`, `.ndjson`	`index.jsonl`, `index.ndjson`
asciinema recording	`.cast`	`index.cast`

The explicit file URL always serves the original source for copying or downloading; its extensionless route serves the rendered view.

Markdown documents also render fenced mermaid code blocks as diagrams. When multiple files resolve to the same route, the precedence is HTML, Markdown, Mermaid, CSV, JSON, JSON Lines, then asciinema.