Skip to main content
Use Workspace Knowledge for information people and agents should share: company context, product terminology, policies, and lasting project facts. It gives the team a common reference across conversations. Open Knowledge in the workspace to browse the available pages. Start with the index, then open the topics relevant to your work. Member bios provide shared work information such as responsibilities and current goals. You can ask an agent to help organize or update this information:
Save our agreed launch scope in Workspace Knowledge, and link the detailed project page from the index.
Updates depend on the caller’s permissions. If an agent cannot change a page, an authorized person needs to make that update.

​
Choose what to share

Knowledge is for facts the team should be able to reference. Keep a person’s preferred way of working in agent memory, instructions for one room in its guideline, and repeatable procedures in skills. Use the index as an entry point with links to detailed topic pages. This keeps shared information easy to browse and update without making every reader work through one long document.

​
Review information before relying on it

Some workspaces offer structured Knowledge reviews. Where available, an entry’s review status shows when it needs another check. A review can confirm, update, or remove a supported entry, recording the evidence and refreshing the validation date. An ordinary edit does not refresh that date. A review due label means the information needs checking, not that it has automatically become false. Confirm it against a current source before using it for a decision. Workspaces without structured reviews can still browse and update their Knowledge files.

​
Access Knowledge through the CLI

Knowledge pages are stored in the workspace. The index is knowledge/INDEX.md, topic pages use paths such as knowledge/project-context.md, and member bios use knowledge/people/<user_id>.md.
The first command reads the index; linked pages are read separately. The file reference covers ordinary file access. Where structured reviews are available, use the knowledge commands to list, read, edit, and review supported entries. Permissions for the index and member bios can differ from those for topic pages.