Documents

Waper documents are Markdown. Edit them in the browser, or have your agent write them. Every document belongs to a knowledge base and can sit in a folder.

Editing

  • Create a document in a knowledge base from the sidebar (the Documents section of a knowledge base page has "New document" too): a title plus rich-text editing (headings, lists, tables, code blocks, quotes);
  • The source of truth is Markdown, but the editor is a rich view — you never think about syntax;
  • The editor only offers what Markdown can store: a table's first row is its header, and cells can't be merged or aligned; an image has an address and alt text, with no caption, alignment or resizing; characters are saved as you type them (--, ... and straight quotes are not replaced with typographic ones);
  • Keyboard: with text selected, ⌘K (Ctrl+K on Windows) adds a link; Alt+F10 moves focus to the floating toolbar, arrow keys move between buttons, and Esc returns to the text;
  • Changes are saved automatically.

Publishing waits for your edits to save. If saving fails or conflicts with another revision, your draft stays in place; resolve the notice before publishing. Moving or publishing a document keeps your current edits. If an agent changes it while you are typing, you can choose how to resolve the conflict.

Version history

Every document keeps its earlier versions, so you can go back to how it was:

  1. Select "Version history" at the top right of the document;
  2. Pick a version;
  3. Select "Restore this version".

Your own edits within 10 minutes become one version; every edit your agent makes is a version of its own, marked "Agent". How far back you can go depends on your plan: Free keeps 7 days, Personal 90 days, Pro keeps everything.

Let your agent write

  • Say it in a chat: "write up this week's EV progress as a document";
  • When it writes a document: when you say "write it up as a document" or "save this", or when what you asked for is finished work you will come back to read or edit, such as a plan, a draft or organized notes. When a document on the topic already exists, it changes that one, translations and rewrites included. Briefs, summaries, answers, comparisons and reports on what it did for you are written out in full in the chat, not saved as documents;
  • Or use the + in the input box to pick items from "Library" and have your agent write from them; "Ask" in the ⋯ menu at the top right of a document asks about that document (it names who: that chat's agent when the document is open beside a chat, otherwise the agent that wrote it, or your main agent if that can't be told);
  • Where it goes: a document is written into the knowledge base of the page you are on; if there is none, to "My knowledge base";
  • Edits you asked for are applied directly, and an open document refreshes to show them. To go back, tell it "change it back" and it restores the version from before the edit as a new version (within 7 days, as long as nobody has changed the document since); or open Version history and restore any version yourself.

Citations & footnotes

When your agent cites brief items or library items in a document it uses footnotes that link to the original source: every fact needs a source.

Import, export & publish

  • Import: in the Documents section of a knowledge base page, select "Import Markdown files" and choose .md or .markdown files (UTF-8 text, up to 500,000 characters each). If one file can't be read, nothing from that batch is imported and the message names the file; a file over the limit is named and skipped, and the rest are imported. For a whole folder, see Knowledge base;
  • Export: ⋯ at the top right of a document → "Export Markdown" exports one document; a whole knowledge base can be exported as Markdown too, with its folder structure;
  • With Google Drive or Notion connected, the ⋯ menu also shows "Export to Google Docs" and "Export to Notion", and you can ask an agent in its chat; headings, lists, bold, links and tables are kept, and one export carries the first 100,000 characters, and a longer document is cut to that and you are told (see Connections). Before exporting to Notion, share a page with Waper in Notion: open any page, choose "…" → "Connections", and pick Waper;
  • Publish to a waper.page site: select "Publish" at the top right; see Publish a site;
  • Images and attachments in a document become publicly reachable when you publish; each file must fit your plan's per-file limit (Free 10 MB, Personal 50 MB, Pro 100 MB).

Moving and deleting

Your agent can see each document's knowledge base and folder before organizing it.

  • ⋯ → "Move to" puts the document in another knowledge base or folder;
  • ⋯ → "Delete" moves the document to the trash, and the message that appears lets you Undo right away. For 30 days you can restore it from More → Trash on a knowledge base page; after that it's deleted for good. While it's in the trash, a published page for it is offline; it comes back when you restore the document.

Capacity

A document body can be up to 500,000 characters on every plan. How long version history is kept depends on your plan; see Plans & credits.