Artifacts
Build, update, view, and share reviewed copies of workspace files, including authenticated MCP Apps.
#Ask the agent to create the artifact
- 01
Finish the workspace preview
Open the HTML file and verify its content, formatting, controls, and loading, success, empty, and error states.
- 02
Ask the agent
Tell the agent to create an artifact from the exact HTML workspace file. Include the artifact name and say whether it should be private, account-shared, or public.
- 03
Confirm the result
Check that the response identifies the source file and confirms that the artifact was created. Open the artifact rather than relying only on the completion message.
#Find the artifact after the agent creates it
- 01
Choose Artifacts
Open Artifacts in the main navigation. You do not need to return to the workspace file browser.
- 02
Search or browse
Search by the artifact name, or browse Starred, Today, and the other time groups.
- 03
Open the result
Select the artifact card or list row to open its preview.
#Open, review, and update the artifact
- 01
Review the copied result
Confirm the artifact contains the reviewed version of the HTML file and that its visible controls work.
- 02
Return to the workspace when needed
Use Open Task to return to the source workspace when the HTML file needs another change.
- 03
Update deliberately
After editing and rechecking the workspace source, update the artifact so the shareable copy receives the new reviewed version.
#Choose the right result type
| Result | Good for |
|---|---|
| Markdown | Readable briefs, plans, and structured notes. |
| Fixed-layout review and distribution. | |
| Document or presentation | Editable business deliverables and presentations. |
| HTML / MCP App | Interactive reports or apps that may call connection tools. |
#Choose an authenticated account share
Open Share from the artifact preview. Choose the authenticated account option when the app calls connection tools. The generated account link requires the viewer to sign in to the account.
Copy the Share Link, open it as an intended account member, and exercise a representative read or action. The app calls tools with that signed-in viewer’s connections and effective permissions—not the artifact creator’s access.
- 01
Open Share
Choose Share from the artifact preview.
- 02
Choose the account
Select For Account and the intended BotDojo account rather than a public link.
- 03
Copy the link
Copy the authenticated Share Link shown in the dialog.
- 04
Verify as the viewer
Open the link while signed in as an intended viewer and confirm the required connection and tool permissions work.
#Sharing MCP Apps
In an authenticated account share, an MCP App calls connection tools as the signed-in viewer. The viewer must have access to the required connection and permission to use its tools.
A public link cannot call connection tools because there is no signed-in BotDojo viewer whose connections and permissions the app can use. The public page may display static artifact content, but live connection-powered controls do not work there.
| Share type | MCP App behavior |
|---|---|
| Authenticated account share | The signed-in viewer can use connection-powered controls when their account access and tool permissions allow them. |
| Public share | Static content can be viewed, but the app cannot call authenticated connection tools. |