Workspace Knowledge

Knowledge holds the facts and guidance your agents need: your offers, brand voice, evidence, and response rules. Each workspace has one Knowledge base. Keep different clients in separate workspaces.

Start and edit

Open Knowledge in your workspace and choose Create knowledge. No GitHub account is needed. Create a Markdown document, give it a path such as business/voice.md, and edit the starter content. Ordinary documents need YAML frontmatter with a nonempty type:

---
type: guide
title: Reply guidance
---

Use a concise, friendly tone. Ask when an offer detail is missing.

Save makes the change available immediately. There is no separate publish step. Owners, admins, and members can create and edit; viewers can read and download. If someone changes the same document before you save, review the conflict and reconcile your text with the current version.

You can also ask the product agent to help build your Knowledge from a business brief. Review what it saves, including assumptions and sources. An agent edit is not proof that a fact has been verified.

Use it in jobs

New jobs authored by the product agent default to read-only Knowledge access. Ask the agent to exclude Knowledge when it is not relevant. Existing jobs are not automatically changed; inspect the job definition and ask the product agent to enable access if needed.

A Knowledge-enabled run captures the latest committed revision when it first starts. All its rows, retries, and resumes keep that revision. After correcting a fact, start a fresh run of the same saved job version to use the update. The previous run keeps its original context and results. Jobs cannot write Knowledge in this release.

Use it from another agent

Connect to Everyn MCP, then explicitly choose Read or Read and edit for that connection in MCP settings. Access starts Off and applies only to the selected workspace. See Knowledge through MCP for setup, tools, and client availability.

Download and recovery

Download ZIP saves the current documents as a portable OKF ZIP with their original paths and bytes. New bases use OKF 0.2; supported existing 0.1 content and custom metadata are preserved. The download contains the current revision, not a history archive.

Everyn retains prior revisions, but this release has no user-facing history or restore control. Download a copy before major changes. Document deletion requires confirmation. History and restore are planned for a later release.

Current limits

The managed base accepts UTF-8 Markdown files only: up to 1,000 files, 1 MiB per file, and 16 MiB total. Paths are limited to 1,024 UTF-8 bytes and 32 components. These are current validation limits, not a storage allowance or price commitment. MCP operations have smaller request limits.

GitHub connections and synchronization, import of ZIP/PDF/Office files, asset uploads, bulk-writing jobs, and advanced search/editing are not included in this release. Downloading your managed Knowledge does not require GitHub.