Artifacts

Threads end in real documents.

An artifact is a persistent, evolving document scoped to a channel. The agent and you co-author it; every change becomes a versioned diff you can review and roll back. Strategy docs, RFCs, goal trackers, meal plans — all first-class, none ephemeral.

See it in /compareGet started
What an artifact looks like

The output you keep, not the chat you scroll past.

Strategy doc

Goals, hypotheses, in-flight bets. Threads that change the strategy can update it directly, with a diff and restore path.

Goal tracker

A living dashboard of where you are vs. where you said you wanted to be. The agent updates it when new evidence comes in.

RFC / spec

Engineering RFC the agent maintains as decisions evolve. Diff history shows what changed and when.

Sprint plan

Plan, scope, daily progress notes. Every standup can leave the plan sharper than it found it.

Meal / training plan

Continuously revised against weekly lab work, soreness reports, and goal drift.

Investor brief

Monthly snapshot maintained by a scheduled agent; each run lands as a version you can inspect before sharing externally.

Shape

Markdown, versioned, bidirectional.

An artifact is a Markdown document with a version history. The agent can edit it directly; you can edit it directly in the app. The artifact is not an ephemeral “canvas” that disappears when you close the chat — it’s a first-class object in your workspace.

ChatGPT Canvas / Claude Artifacts

Scoped to the chat. Closes with the chat. Hard to find next week.

Boardbox artifact

Persistent, channel-scoped, versioned, listed in the channel index forever.

apply_artifact_update·RFC-014 · +12 lines · -3 linesapply_artifact_update·Goal tracker · status: at risk → on trackapply_artifact_update·Meal plan · swapped Tuesday lunch
Writes are versioned

The AI commits. The history shows the diff.

Every AI write to an artifact lands as a structured version against the current document. You see exactly what changed after it lands: added lines, removed lines, attribution, and source thread. Edit the document, restore a previous version, or let the new version stand.

Time travel

Every version stays. Forever.

Artifacts are versioned by default. The version that was canon when an agent made a recommendation is still there — useful when you want to know what the model saw before its advice. Storage is cheap. Lost work is expensive. We default to keeping everything.

Versioned

Every change to an artifact lands as a new version. Nothing is overwritten silently.

Reviewable

AI changes show as a diff against the previous version, with restore available if the edit is wrong.

Provenance

Each version is attributed to the thread (and agent) that wrote it.

Reach

Push to Notion, GitHub, or Linear via MCP.

Artifacts don’t have to live only in Boardbox. Connect Notion and your strategy doc syncs to a Notion page. Connect GitHub and an RFC syncs to a Markdown file in a repo. The artifact stays the canonical version; the integration target stays in sync via the same version history. External writes can still require approval before anything leaves Boardbox.

FAQ

Common questions

What's the difference between artifacts and threads?
A thread is a conversation that resolves to something. An artifact is the something — a persistent document with version history that lives independently of any one thread. Many threads can update the same artifact over weeks or months; the artifact's diff log shows what each thread changed.
Can I export an artifact?
Yes. Artifacts export to Markdown, PDF, or push directly to Notion / GitHub / Linear via the relevant integration. The export carries the version history with it.
How does the AI know which artifact to update?
Artifacts are listed in the channel index — so the agent always knows what artifacts exist in the current channel. The agent picks the right one based on what the thread is about, then applies a versioned update against the current document.
What if the AI updates an artifact incorrectly?
Artifacts are versioned, so prior states are preserved as the document evolves. If the agent gets the scope or wording wrong, inspect the diff, edit the current document, or restore an earlier version.
Can I share an artifact with someone outside Boardbox?
Native sharing is on the roadmap. Today, you can push artifact content out via connected integrations (Notion, GitHub) where supported.
See also

Related features

Threads

Most artifacts are born from a thread. The thread resolves; the artifact starts a version history.

Learn more

Scheduled Agents

Scheduled agents update artifacts on a cron. Each run is a new version — the artifact's history is the agent's memory.

Learn more

Integrations

Artifacts can sync to Notion, Linear, or GitHub via MCP — your living doc, in your team's tool of choice.

Learn more

The chatbox was a phase.
Build a workspace.

Boardbox keeps your context, holds its ground, and produces work that lasts.

Get started →