A knowledge base is a set of documents you can edit (with folders), plus background for your agent, the library items filed in it and the watches linked to it. One sentence separates it from the library: a knowledge base holds documents you can edit; the library holds everything else.
Knowledge bases live in the cloud only. Open them from any device, and your agent keeps working in them while your computer is off.
Every account comes with "My knowledge base", which can't be deleted. You never have to create anything first: any document that isn't written inside another knowledge base goes here.
A knowledge base is a way to organise once you need one, not a prerequisite. When a project or a long-running interest deserves its own place, create one: "Competitor research", "Reading", "Job search".
The knowledge base tree in the sidebar contains only folders and documents, and each document is one Markdown file. Only the knowledge base you're in is expanded by default.
Open a knowledge base and you see:
A note written for your agent: what this knowledge base is for, what you care about, how you want things framed. Up to 1,000 characters. In a conversation here, the background goes to your agent with every turn.
Pages, files and recordings in your library can be filed in a knowledge base. Add lets you "Upload a file", "Paste a link" or "Pick from your library"; anything you add here is filed in this knowledge base directly. Filing is optional; see Library.
A watch doesn't belong to a knowledge base, but you can link one. A knowledge base can link several watches, and a watch can be linked to several knowledge bases. Select Link and pick from the watches you follow. Once linked, your agent looks through those watches' briefs first when you talk to it here. Unlinking doesn't unfollow: the watch stays in your radar. The other way round, when you unfollow a watch, its links to knowledge bases are removed too.
The automations that write their documents into this knowledge base are listed here. Add opens a new one with this knowledge base already chosen.
Already have a folder of Markdown, such as an Obsidian vault?
.zip instead;title in its front matter uses it; otherwise the file name is the title..md, .markdown) are imported; other files are skipped. Chinese file and folder names inside a .zip keep their names when they are encoded as UTF-8 or GBK. Hidden files and folders (names starting with ., such as .obsidian or .git), node_modules and __MACOSX are left out, and the page tells you how many and which. Files must be UTF-8: if one can't be read, nothing is imported and you're told which file it is.Notes/a.md and notes/a.md) stop the import and the files are named. Rename them and try again..zip can be up to 100 MB (for a bigger one, unzip it and choose the folder), and the Markdown inside can unpack to at most 200 MB (for more, unzip it and import a subfolder)..zip exported from waper (see "Exporting" below) can be imported straight back.Only want a few Markdown files in a knowledge base you already have? In the Documents section of that knowledge base's page, select Import Markdown files. The files go to the top level, and the rules are the same as above (only .md and .markdown; if one can't be read, nothing is imported; a file over 500,000 characters is named and skipped, and the rest are imported). A knowledge base holds at most 2,000 documents: if the import would go over that, it stops, and what was already imported stays.
Would rather not upload a folder? Then don't import it. Choose "Work in a folder on your computer" from the + in the input box, and your agent reads and edits it in place while your computer is online. See Your computers.
You can export a knowledge base as Markdown at any time (More → Export as Markdown on its page). You get an archive with the same folder structure. One export packs up to about 8 million characters of text; above that the page tells you how much there is, and you can move some documents to another knowledge base and export the two separately. A single document can be exported on its own too; see Documents.
Every knowledge base except "My knowledge base" can be deleted (More → Delete knowledge base on its page). Nothing in it is deleted: its documents and folders move to "My knowledge base", the items filed in it become unfiled, linked watches stay in your radar, conversations started in it stay in your conversation list, and its automations stay, but no longer belong to this knowledge base.