Artifacts

The reports, status pages, and write-ups your Praxis agents produce, saved as versioned files you can browse, open, and share.

An artifact is a deliverable a Praxis agent produces and saves for you: a Markdown or HTML document that persists after the chat or run that created it ends. It has a title, a version, and a stable link, so you can find it again, open it, and share it later. You reach every artifact your organization has produced from the Artifacts page in the web console.

📘

These are not the same as build artifacts, the container images and zip bundles your CI registers so the right image deploys to the right place. For those, see Artifact CI.


How artifacts are created

You do not create artifacts by hand. An agent produces one whenever it generates something worth keeping, in one of two situations:

  • In a chat, when you ask for a deliverable: "give me a cost summary for production", "write up the findings", "build me a status page".
  • In a scheduled run, when a duty produces a recurring report, such as a weekly cost sweep or a daily cluster-health page.

Each artifact is either Markdown, for textual reports, summaries, and plans, or HTML, for status pages and dashboards where layout matters. The agent picks whichever fits the content.

An artifact carries a stable name behind the scenes, and that name is what versions it. When an agent produces something new under a name it has used before, in the same chat or the same schedule, the result becomes the next version rather than a separate artifact. A report that runs every Monday builds up as v1, v2, v3 under one name, so its history stays together.


Find your artifacts

The Artifacts page lists everything your organization has produced, newest first. Search by title or name, and narrow the list by format (Markdown or HTML) or by where it came from (Chat or Schedule). Each tile shows the format, the version, the source, when it was produced, and the agent that made it.

By default the page uses Group by name, so a report that has run many times shows as a single tile with its version count. Switch to Show all versions to see every individual version as its own row.

You can also reach an artifact from the place that made it: a chat links the outputs it produced, and a scheduled duty shows the artifacts from its runs, including the full report a finding points to.


Open and read one

Selecting an artifact opens a viewer, either in place or on its own full page. Markdown opens as formatted text. HTML renders inside a locked-down sandbox that cannot run scripts, make network calls, or submit forms, so opening one is safe even though an agent generated the markup.

If more than one version exists, a version picker beside the title lets you jump between them. When you are looking at anything other than the newest version, a banner tells you so and links you to the latest.


Share and download

The viewer offers two kinds of link, for two different needs:

  • Copy gives you the latest link. It always resolves to the newest version under that name, so it keeps pointing at current results as new versions arrive. Use it to share a living report.
  • Copy version-pinned link, in the more-actions menu, gives you a link frozen to the exact version you are viewing. Use it to cite a result that should not change under you.

From the same viewer, Download saves the artifact as a .md or .html file, and Show provenance lists where the artifact came from, its source and the chat or run behind it, with each id ready to copy into a ticket or another link.


Privacy and deletion

Every artifact is scoped to the organization that produced it, so one organization's artifacts never appear in another's console. For how Praxis scopes data and runs under your own permissions, see How Praxis works.

You can remove an artifact with Delete in the viewer's more-actions menu. Only the person who created it or an organization admin can delete it.

🚧

Deleting an artifact permanently removes it and its content, and any link to it stops working for everyone. This cannot be undone. To stop a recurring report from growing without losing what it has already produced, pause the duty behind it instead.


  • Duties - Scheduled runs that produce recurring reports as artifacts
  • How Praxis works - Organization scoping, your permissions, and the safety model
  • Agentic Apps - Packaged apps whose runs also produce artifacts
  • Artifact CI - Registering build artifacts (container images and zip bundles) for deployment