Share pages the assistant makes

An artifact in Busymate AI is one self-contained web page bro builds on request — a report, a diagram, a how-to — served at your assistant's address under /artifact/<slug>. You choose who can open it (only you, your team, or anyone with the link), comment on it inline, send a thread back to bro for a fix, and manage everything from your AI tools (MCP).

What an artifact is

• One web page with everything inline. External scripts, stylesheets and fetches are rejected when it publishes, so a page never breaks because a third party changed.
• Addressed by a short lowercase name (slug) that is unique inside your workspace. Platform pages live at busymate.ai/artifact/<slug>; your workspace's live at your address.
• Owned by whoever created it, inside your workspace. Older addresses that served pages redirect to the current one.

1. Create

• In chat — ask bro for the page you want. It builds the page and publishes it at your address.
• From your AI tools — create_artifact with slug, title, html, description, tags and visibility. The call succeeded only if the response says created: true; anything else is an error to read, not a page to assume.

2. Set visibility

Change it any time in Console → Artifacts or with set_artifact_visibility. A private page never leaks a title or a share card, even to a stale scraper.

3. Comment and iterate

Open the artifact and select text, an element or a region to start a thread anchored to it. Send to bro activates the thread for the AI: bro replies in the thread and applies the change as one update_artifact. Resolve the thread when the page is right; reopen it if it is not.

4. Meet the quality bar

Every artifact bro publishes is held to the same bar:

• An in-page language switcher covering all 14 locales, with right-to-left layout for Arabic.
• Diagrams as inline SVG that follows light and dark themes; never an external image.
• No horizontal scroll at 390 px wide; contrast at WCAG AA.
• Concise: illustrations and numbered steps over walls of text.

Console and AI tools

The Console lists, previews, retitles and re-scopes pages. Your AI tools (MCP) do the same: list_artifacts, get_artifact, update_artifact, set_artifact_visibility, delete_artifact, plus list_artifact_comments, add_artifact_comment, reply_artifact_comment and resolve_artifact_comment. Connect a client once:

claude mcp add --transport http busymate-ai https://busymate.ai/mcp

Examples

Public artifacts on the platform host: the Inbox proof of 2026-09-02, the DevTools integration and Build your MCP server. The gallery at /artifact lists every public one.

Verify

1. The page renders in light and dark themes with no sideways scroll on a phone.
2. Switching it to "anyone with the link" adds it to the gallery and the sitemap; switching back removes it.
3. A comment sent to bro gets a reply and one update; resolving the thread closes it.
4. The slug URL opens at your address.

Next

• Conversation-derived product intelligence — reports bro can publish as artifacts.
• Managing from chat — the same management tools, conversationally.
• The gallery — public artifacts, live.