Artifact types, app and markdown

An artifact is one app, document, or stored file with its own URL and History. Its type controls how AgentGrid.io displays and edits it.

Use an app for presentations, dashboards, forms, calculators, sites, and interactive explainers. Use markdown for plans, reports, notes, specifications, and other material meant to be read and edited. PDFs, spreadsheets, images, and unsupported files remain assets.

How artifacts are created

• New Doc creates markdown.
• Upload File stores one file; unrenderable content becomes an asset.
• Folder or ZIP import creates an app or markdown artifact from one multi-file source.
• Import from URL and Import from Figma create app artifacts.
• A connected agent can create or import into an authorized workspace.

A Knowledge Base is an app-backed experience created from the current server template, not a separate low-level artifact type. See Create and use a Knowledge Base.

Editing and publishing

Markdown edits autosave continuously; Save or ⌘S creates a checkpoint, which is a named History entry. Fenced mermaid source renders in the editor, History, and published markdown pages. Canvas is only for app artifacts whose HTML or React project can load in AgentGrid.io's visual editor. Markdown documents and stored files are not Canvas artifacts. Apps with unsupported project structures stay Preview-only.

Both apps and markdown artifacts can be published. Assets are stored and versioned but do not gain an app or document renderer.

Type and import constraints

Choose the intended type at creation. If the result has the wrong type, create a new artifact with the correct type rather than assuming the type can be converted in place. An entry point is the file that starts an app when it opens, such as index.html. An app may render blank when that file is missing or misplaced. Markdown requires at least one .md file.

Free website and Figma imports share a separate five-success allowance; folder/ZIP import does not use that allowance. Artifact capacity and import allowance are separate. See Plans and usage and Limits and quotas.

Questions and answers

Which type should I choose for an interactive experience? Choose app and include an entry point such as index.html.

Can I convert an artifact to another type later? Do not assume in-place conversion. Create a new artifact with the correct type.

Why is an app blank or Preview-only? A blank app may lack a correctly placed entry point. An unsupported HTML or React project structure can remain Preview-only.

Is a Knowledge Base a separate artifact type? No. It is an app-backed experience created from the current server template.

Type decision

An artifact is one app, document, or stored file with its own URL and History.

Choose app for interactive or visual work and markdown for readable documents. PDFs, spreadsheets, images, datasets, and other unsupported files remain assets.

Creation mapping

• Human New Doc → markdown.
• Human Upload File → stored file, often an asset.
• Folder/ZIP import → explicit app or markdown.
• URL or Figma import → app.
• Authorized agent creation/import → selected type in an explicit workspace when more than one is writable.

A Knowledge Base is a server-template-backed app experience, not a fourth low-level artifact type. Use Create and use a Knowledge Base.

Behavioral boundaries

Markdown autosaves; Save or ⌘S requests an explicit checkpoint, meaning a named History entry. Canvas is only for app artifacts whose HTML or React project can load in the visual editor. Markdown documents and assets are not Canvas artifacts. Unsupported app project structures stay Preview-only. A Canvas draft is unsaved human editing state. Do not claim agent access to it or promise that it is preserved. Agents operate on saved artifact state unless explicitly told otherwise.

Apps and markdown can be published. Assets remain addressable and versioned without gaining a renderer.

Validation and recovery

Verify type, workspace, required files, and rendered result after creation. An entry point is the file that starts an app. A blank app commonly indicates that this file, including index.html, is missing or misplaced. A markdown import needs .md content. If the wrong type was created, create a new artifact of the intended type.

Website and Figma imports share the Free team's five-success allowance; artifact capacity is separate, and deleting an import does not refund allowance. Use Plans and usage and Limits; relay quota refusal instead of retrying.

Questions and answers

What should determine the artifact type? Verify the source structure: an app needs an entry point, markdown needs .md content, and unsupported files remain assets.

What must be verified after creation? Check the artifact type, destination workspace, required files, and rendered result.

Can an agent operate on an unsaved Canvas draft? No. Treat Canvas drafts as human-controlled unsaved state and operate on saved artifact content.

How should an import quota refusal be handled? Relay the plan or upgrade path and do not retry; deleting the imported artifact does not refund the allowance.