Library
Library collects your artefacts, mutters, messages, feedback, activity, conversations, provider traces, memories, Pantry templates and ENV packs. Browse by section or filter by Agent.
Open Library for notes and files, inspect raw provider logs when an AI session needs debugging, or pull a reusable template out of the Pantry.
What lives in Library
| Item | What it is |
|---|---|
| Artefacts | Files and notes produced during work: reports, screenshots, mockups, CSVs, snippets, interactive previews. |
| Mutters | Short progress notes: what was tried, where things broke, what's left. |
| Feedback | Ratings and reviews of Agent output. |
| Messages | Conversation messages worth surfacing outside the chat. |
| Conversations | Transcripts of your chats with Agents. |
| Activity | Higher-level events: messages sent, Tasks run, rollouts. |
| Raw provider traces | The exact request/response logs from an Agent's provider. For debugging an AI session. |
| Memories | Persistent notes the Agent or the user marked as worth remembering. |
| Pantry templates | Your saved reusable Templates. |
| ENV packs | Named maps of readable environment values that you pick when creating a Playground. |
Each section is searchable, and any section can be narrowed to a single Agent with the Agent filter.
Authoring artefacts
Create an artefact directly in the Artefacts section:
- Title: your reference.
- Description: short summary (optional).
- Body: Markdown content. The editor surfaces a body placeholder until you start writing.
Agent-created artefacts appear in the same library and carry a creator badge. They are read-only, but you can download them or change their skill flag.
Raw provider traces
Provider traces capture the exact request and response. Use them to debug wrong answers, refused tool calls, and context-window failures.
Traces are sensitive: they contain prompts and replies verbatim. Treat them like the data they contain.
Pantry
The Pantry holds private reusable Templates that are too specialized for the public Bazaar.
Pantry templates can be:
- Edited in place (name, description, image, category).
- Versioned: publish a new version whenever you want to change the body; each version is an immutable snapshot, and editing the template's name or description doesn't create one.
- Imported into a Spec at launch time.
ENV packs
The ENV packs section lists the packs of the owner selected in the Team pill, with an owner column showing Personal or the Team name. Create, edit and delete packs here, then pick them when you create a Playground, or as packs for scheduled runs on a job-mode Spec. Packs are readable values, not a secret vault. See ENV packs.
Memories
A memory is a tagged note available to future conversations, such as a project fact, preference, or lasting decision.
Memories are written explicitly: either by the user adding a note, or by the Agent storing a fact when instructed.
Search
Each section has its own search box: search artefacts in Artefacts, memories in Memories, and so on. The search box on the Library home page searches your artefacts. Narrow any section to a single Agent with the Agent filter.
FAQ
Library vs Conversations?
A Conversation is a chat thread with an Agent. Library is your account's library, collecting the outputs of work across all your Conversations and Agents: including messages worth surfacing outside the chat. Conversations focus on dialogue; Library collects what the work produced.
Where do artefacts live?
Artefacts live in your account's library. Use the Agent filter to narrow the list to the Agent that produced them.
Are Pantry templates public?
No. Pantry templates are private to your account until you publish a version. Publishing a version puts that version in the Bazaar; the rest of the template stays private.
Related
- Agents: where most of the library's content originates.
- Bazaar: public counterpart to private Pantry.
- ENV packs: picking packs per Playground and grants.
- Specs & Templates: Templates can be authored into the Pantry first, then promoted to the Bazaar.