Skip to main content
The knowledge base provides structured reference materials to Waker, using a Notebook-style management approach.

Knowledge Base Interface

Click “Knowledge Base” in the left navigation bar to enter the page:
  • Notebook list: Displays all created knowledge Notebooks. Each Notebook shows its name, document count, and associated Waker.
  • New Notebook button: Click to create a new knowledge category.
  • Search: Supports full-text search of knowledge content.

Creating and Managing Notebooks

Creation steps:
1

Click New Notebook

Click the “New Notebook” button on the knowledge base page.
2

Enter a Notebook name

For example, “Frontend Development Guidelines” or “Product Requirements Document.”
3

Complete creation

Click “Create” to finish.
Managing Notebook content: After entering a Notebook, you can see the list of uploaded documents and the operations area:
  • Document list: Shows all uploaded files, including file name, type, size, and upload time.
  • Upload button: Add new document files.
  • Delete operation: Remove documents you no longer need.
  • Waker binding settings: Configure which Wakers can reference this Notebook.

Uploading Documents

Click the “Upload” button and select a file in the dialog that appears:
  • Supports formats such as PDF, Markdown, code files, and text files
  • Supports batch upload of multiple files
  • After upload, the system automatically builds a search index
  • Once indexing is complete, bound Wakers can reference the knowledge content in a session

Collaboration and Sharing

  • Collaborator management: Invite other users to maintain Notebook content together.
  • Waker binding: Specify which Wakers can reference the knowledge in this Notebook.
  • Version tracking: Documents are automatically re-indexed after updates.

Usage Recommendations

  • Create separate Notebooks by topic or domain to avoid mixing content.
  • Update document content regularly to keep the knowledge current.
  • Only bind Wakers that genuinely need the knowledge, to avoid irrelevant content interfering with Waker’s judgment.
  • Prefer documents in Markdown format, as structured content is easier to retrieve accurately.