Artifacts

When an agent produces more than plain text, LinkCode renders it as an artifact. There are two altitudes to this, backed by one underlying system: some content renders directly in the chat stream, and some renders as a card that opens in a panel.

Inline artifacts

Three kinds of content render inline, right in the conversation, as the agent writes them:

• Mermaid diagrams — rendered live as a diagram, not as code. Clicking an element in the diagram (a node, an edge label) inserts a reference to it into the composer, so you can ask the agent about that specific part without retyping it.
• SVG — sanitized and rendered inline, with the same click-to-reference behavior as diagrams.
• Self-contained HTML — shown as code until you choose to run it, then rendered in a sandboxed frame (scripts allowed, but no access to the page it's embedded in) hosted on its own local artifact--<hash>.localhost address. An Open in panel button promotes it into the Browser panel so you can use it alongside the rest of the interface.

If an inline artifact fails to render (invalid Mermaid syntax, malformed SVG), LinkCode falls back to showing it as a plain code block.

A Mermaid diagram rendered inline in the conversation, with one node selected and referenced in the composer below

Screenshot coming soon

/images/docs/interface-artifacts-inline.png

File artifacts

When a tool call produces a file — writing, editing, or moving one — LinkCode shows it as a small card under that call in the conversation. Clicking the card opens the file in the Files panel. Markdown, PDF, and image files render as their real preview there; plain text renders as-is; anything else shows an "unsupported" notice rather than raw bytes.