The Knowledge Base

When an agent finishes a draft, a research note, or a summary, that document lives in the Knowledge Base. The inbox tells you the work is done; the Knowledge Base is where the work itself sits.

Think of it as the workspace's library. Your own pages live here too — notes, internal docs, anything you'd otherwise keep in a separate doc tool. One folder tree for both.

Where the Knowledge Base lives

The sidebar has a Knowledge Base section under your projects. Inside, you see a tree of folders and pages. Click a page to open it; click a folder to expand it. Drag pages and folders to reorganize.

There's no separate Knowledge Base page or route — the tree in the sidebar is it. That keeps the library in the same place as your projects so navigation stays predictable.

Adding pages and folders

Hover the Knowledge Base header in the sidebar and click the + that appears. The menu has two options: Page and Folder. Pick one and it lands at the top level. You can also create a sub-page from inside any open page using the editor's "+ New sub-page" action, which nests the new page under the current one.

For agent-produced pages, you don't create anything yourself — the agent does it as part of its work.

How agent outputs land in folders

When an agent uses page-creating tools, the new page is saved to one of two places:

The agent's default output folder — if its settings point at a specific folder, drafts go there.
A folder picked at runtime — when the agent's instructions or your prompt steer it to a particular location.

Open the inbox after an agent run; the AI completed notification links you straight to the page that was created.

What a folder shows

Click a folder rather than a page and you'll see a list of its children grouped by date — Today, Yesterday, Earlier this week, and so on. Quick actions in the header let you add a new page or folder inside without going back to the sidebar.

Finding pages

Press Cmd+K (Mac) or Ctrl+K (Windows / Linux) to open the global search palette. Search runs across pages, projects, and tasks; type a title fragment or a phrase from a page's content. Each result shows the page's folder breadcrumb so you can tell which area it came from.

For pages you reference often, the sidebar tree is faster than search — drag the page to a folder near the top, or favourite the project it belongs to.

Linking pages together

Inside the editor, type [[ and pick a page from the dropdown. You get a hyperlink to that page, and the linked page picks up a backlink at the bottom — so you can see everywhere it's referenced. Useful when one canonical doc (a brand voice spec, a release SOP) gets cited across many other pages.

Tips and gotchas

The Files page is separate. Files (under the same workspace) is the attachment browser — every file that's been uploaded to chats, comments, or pages. It's a different surface from the Knowledge Base; pages live in the KB, attachments live in Files.
Some folders are system-managed. A small banner at the top of the page tells you when you're looking at a system folder — typically used for workspace memory and agent-managed content. You can read what's in there but generally shouldn't restructure it.
Reorganize aggressively. Folders are cheap and pages move freely; if your KB starts to feel like a junk drawer, drag pages into folders that group them by project, topic, or recurrence (weekly briefs / monthly retros / pack docs).
Folders aren't files. Renaming or moving a folder doesn't break links to the pages inside it — pages keep their URLs even when their folder changes.