Artifacts

Introduction

An artifact is a document an agent publishes through Gatana: a report, a dashboard, a small tool, or any self-contained page. Each artifact gets a stable link on your organization's domain:

https://{organization}.gatana.ai/artifacts/{id}

The link never changes: not when the content is updated, not when the artifact is renamed, and not when its access changes. Send the link once and it keeps pointing at the newest version.

Agents create artifacts with the built-in Artifacts server. Its tools are create_artifact, update_artifact, share_artifact, unshare_artifact, and list_artifacts. The same operations exist as /artifacts routes in the Public API.

All artifacts you can open are listed under Artifacts in the dashboard sidebar.

Who Can Open An Artifact

A new artifact is private to its creator. Access is widened in two independent ways, and the Share button in the viewer controls both:

General access sets the audience for the link:

Shares give read access to chosen people or teams, whatever the general access is. A team share covers every current member of the team. Agents share by email address and team name with share_artifact; people use the Share button in the viewer. Shares on an organization-wide or public artifact change nothing at that moment, but they are kept, so setting the artifact back to private restores exactly the earlier audience.

Sharing gives read access only. Renaming, sharing, changing access, and deleting stay with the creator and organization owners.

Content: Markdown or HTML

An artifact holds either Markdown or a complete HTML document, chosen per version:

• Markdown is stored as written and rendered to a styled page when opened. GitHub-flavored syntax is supported (tables, task lists, fenced code). This is the right choice for documents, reports and notes. The viewer offers Copy Markdown to get the source back.
• HTML is served as published. The page must be self-contained: inline the CSS and JavaScript and embed assets as data URIs, because the page renders in a sandboxed frame with no access to Gatana.

A Markdown version can be at most 10 MB, an HTML version at most 50 MB.

Themes

Each artifact has a theme. The default Gatana theme gives plain semantic HTML and rendered Markdown a finished look (typography, tables, code blocks, links) without the author writing any CSS. Choose None to serve the document exactly as published. The theme is changed in the viewer's title menu, applies to every version at once, and never creates a new version. The author's own styles always win over the theme.

Versions

Every content update creates a new version behind the same link, and the link always shows the newest one. Older versions stay available under Version history in the viewer's title menu. Renaming an artifact or changing its theme or access does not create a version.

Deleting an artifact deletes all versions, and the link stops working.

The Viewer

Opening an artifact link shows the page with a small header: who created it, when it was last updated, and a menu on the title with rename, theme, copy link, version history, and delete. Visitors without access are asked to sign in (or told the artifact has not been shared with them, if they are signed in already).

Artifact pages render in a sandboxed frame on a separate origin, so a page written by an agent can never act on your Gatana session.

Enabling Artifacts

Agents can only create artifacts when the built-in Artifacts server is installed, enabled, and visible to them:

• New organizations have it installed and shared with the whole organization from the start.
• Existing organizations got it installed with private visibility. An owner decides who may create artifacts: set the server's visibility to organization, or keep it private and attach chosen users and teams.

The Artifacts page in the dashboard tells owners when the server still needs one of these steps. Creating an artifact needs a caller with a user identity, so a connection that does not identify a user cannot create one.

Encrypted at rest like everything else in your organization: artifact content is stored under your organization's key, see Confidentiality.