Library - Hyperagent Knowledge Base

The Library keeps the outputs from your threads in one place: documents, tables, webpages, images, videos, maps, apps, and files. Use it when you want the finished work, not the full conversation behind it.

Where finished work lands

A thread is the workspace where an agent researches, reasons, uses tools, and produces outputs. Those outputs are artifacts: the files the agent creates as it works.

The Library gives those artifacts a dedicated view. They still belong to the thread that created them, so you can always return to the original context, but you do not have to retrace the whole run to find the finished piece.

That matters once your workspace starts filling up with useful work: renewal summaries, competitor tables, or client reports. The Library is where you search, filter, open, share, and reuse what your agents have already created.

What shows up in the library

The Library collects the artifacts agents create while they execute. You do not need to save them separately.

You can search the Library by artifact title or filename. Filters help narrow the view by type, published status, source, saved items, global items, agent, project, thread, and archived artifacts.

📄Documents

Markdown files the agent writes and updates for notes, explanations, research findings, briefs, account summaries, and other written work. Documents can be scoped to a thread, project, or globally.

📊Tables

Typed rows and columns the agent builds and updates: pricing comparisons, lead lists, account trackers, or research datasets. Tables can be exported to CSV or JSON.

🌐Webpages

Published HTML pages the agent designs and writes: reports, dashboards, visualizations, client pages, or embedded map views.

📽️Slides

Decks the agent designs slide by slide for reviews, briefings, pitches, or internal updates.

🖼️Images and media

Generated images, edited visuals, videos, audio, and talking-head avatar outputs.

🗺️Maps

Interactive maps, routes, location views, Street View outputs, and other location-based artifacts. Maps appear under Webpages because they are HTML artifacts.

⚡HyperApps

Interactive applications the agent creates when the output needs live interaction, search, or tool access.

📎Files

Uploads, exports, PDFs, CSVs, code files, and other generated or attached files that are renderable types, such as images, text, PDF, and JSON.

What stays out of the Library

Thread Context Documents and Project Context Documents are working memory, so they stay out of the Library. System-generated files such as thumbnails and agent configuration exports are also excluded.

Library grid showing artifact cards, search, filters, and archive controls. — The Library gives you an artifact-first view of the documents, pages, media, and files your agents have created across threads.

How artifacts get there

You do not create a Library item separately from the work. The agent creates outputs while working in a thread, and those outputs appear in the Library automatically.

Every invocation type produces Library items the same way. Scheduled runs, webhooks, Live Mode ticks, Slack mentions, Telegram messages, and email-triggered runs all create threads. Artifacts from those threads appear in the Library just like artifacts from manual conversations.

When you open a Library item, you can click through to the source thread to see the prompt, context, tool calls, decisions, and feedback that shaped the output.

Library artifact detail view showing publish, open in new tab, download, version history, and used-in-threads actions. — Open an artifact to publish it, download it, review versions, or jump back to the thread where it was used.

Finding the right artifact

The Library becomes more useful as agents create more artifacts. Search and filters help you get back to the right output without digging through old threads.

Search. Match against the artifact title or filename.
Category. Narrow to images, video, audio, webpages, slides, tables, documents, or apps.
Scope. View everything, saved items, global items, items from a specific agent, a specific project, or a specific thread.
Published status. Show published items, unpublished items, or both.
Sort. Sort newest or oldest.
Archived threads. Artifacts from archived threads are hidden by default. Toggle archived items on when you need them.

Library search does not search inside artifact content. It does not inspect the body of a document, the rows of a table, or the HTML of a webpage. If you remember the topic but not the exact title, narrow by project, agent, artifact type, scope, or published status.

What you can do with artifacts

Once an artifact is in the Library, you can use it beyond the thread that created it.

↩️Return to the source

Open the thread behind an artifact to see the prompt, context, tool calls, decisions, and feedback that shaped the output.

🔗Share or publish

Publish supported artifacts with a link when the output needs to reach stakeholders, clients, or teammates. Domain restrictions can limit access by email domain.

📤Export

Export tables to CSV or JSON, read documents as markdown, and download files directly.

🕰️Track versions

Documents save a version on every edit. Webpages, slides, and HyperApps save the previous version before each edit.

📌Reuse as context

Add a document, table, or file as context, or @ mention a document or table in a new thread.

⭐Save favorites

Star important artifacts so they show up quickly in the Saved filter.

Tables and media do not have version history. If you need a clear audit trail for changing written work, pages, decks, or apps, use the artifact types that keep versions.

Reusing artifacts as context

Artifacts stay connected to the thread that created them, so you can always get back to the source trail: the prompt, files, tool calls, decisions, feedback, and revisions behind the output.

When you want to reuse an artifact in a new run, the path depends on what kind of artifact it is.

Documents. Use documents when the artifact should become written context. @ mention a document in a thread, add it to an agent as a context file, share it across a project, or make it global. This works well for research notes, brand voice guides, operating principles, customer briefs, and project plans.
Tables. Use tables when the agent needs structured data again. @ mention a table in a thread, add it to an agent as a context file, or mark it global when a pricing table, account tracker, lead list, or dataset should be available broadly.
Files, media, and published outputs. Images, videos, audio, webpages, slides, maps, and files work more like finished deliverables. To reuse one, paste the published URL, attach the file, add a supported file as context, or bring over the exact reference yourself.
HyperApps. HyperApps have their own URL. Once created, you can open the app directly from that URL, no matter which thread produced it.

For anything an agent should always have, use a context file. For anything needed once, @ mention the document or table, paste the URL, or attach the file in the thread.

Library FAQs

Threads keep the run. The Library keeps the artifacts organized and ready to reuse. Use it to search, filter, open, share, export, version, and reuse the documents, tables, webpages, media, maps, apps, and files your agents create.