> For the complete documentation index, see [llms.txt](https://gopersonal.gitbook.io/calvin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gopersonal.gitbook.io/calvin/user-guides/artifacts.md).

# Artifacts

Artifacts are outputs generated within workspaces that can be shared and reused across your team. They might include code components, analytical reports, design assets, configuration files, or any other deliverable that Calvin produces during a chat session.

The Artifacts page in the sidebar provides a centralized view of all artifacts across your store. You can search artifacts by name and filter them by visibility: All shows everything you have access to, Public shows artifacts visible to all team members, Private shows artifacts only you can see, and Shared With Me shows artifacts that other team members have specifically shared with you. The page supports both grid and list views for browsing.

Artifacts are created when they are shared from a workspace. During or after a chat session, outputs can be published as artifacts so they are accessible outside the workspace context. This is useful when one team member creates a component or report that others need to reference or build upon.

You can also reference artifacts directly within chats. The "+" menu in the chat input includes an Artifacts option that lets you attach an existing artifact to your current conversation. This allows Calvin's agents to use previously created outputs as context when working on a new task — for example, referencing a design system artifact when building new UI components, or pulling in a data analysis artifact when creating a follow-up report.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gopersonal.gitbook.io/calvin/user-guides/artifacts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.