View planned changes for Organized folders and connections: awaiting release. Availability depends on the released app and host versions.
One shared foundation, specific project context#
Ondago calls its two knowledge scopes Workspace knowledge and Project knowledge. Both can hold instructions, skills, decisions, and reference material.
| Scope | What belongs here | Where to edit it |
|---|---|---|
| Workspace knowledge | Guidance shared across your workspace: coding conventions, review expectations, reusable skills, and team references. | Settings → Workspace → Knowledge. |
| Project knowledge | Context for one project: architecture decisions, setup instructions, project skills, and exceptions to optional workspace guidance. | Projects → choose a project → Knowledge. |
Put shared guidance in the workspace so projects can inherit it. Add project-specific context in the project rather than copying the workspace files into every project.
Publish workspace knowledge#
- Select the workspace you want to configure.
- Open Settings, then Knowledge under Workspace.
- Add or edit the entries your projects should share. Use Save draft to keep work in progress.
- Choose Review & publish, inspect the changes, and publish when ready.
Workspace owners and admins can publish workspace knowledge. Members can prepare drafts for review. Project maintainers and workspace owners or admins can publish project knowledge. A saved draft is not used as the published guidance for new sessions.
How workspace and project knowledge combine#
Ondago starts with the latest published workspace entries, applies the selected project’s published overrides, then adds that project’s own entries. A project brief is included as reference material when present.
- Inherited: a workspace entry is used as published unless the project explicitly overrides it.
- Override in project: replace an optional inherited entry for this project. The workspace version and other projects stay unchanged.
- Disable in project: leave an optional workspace entry out of this project’s combined knowledge.
- Required: a workspace entry marked required cannot be replaced or disabled by a project.
Adding another file does not implicitly override an inherited entry. Use the explicit override controls. Required entries protect the inheritance rules; instructions in their text are still guidance for the agent, not a replacement for tool permissions.
Example: shared conventions and a checkout project#
| Workspace guidance | Checkout project choice | Knowledge for a new Checkout session |
|---|---|---|
| Require tests for behavior changes; marked required. | Keep the inherited entry. | The testing requirement remains included. |
| Use the team’s standard setup command; optional. | Override this entry with the checkout service’s setup steps. | The project’s setup steps replace the optional workspace entry. |
| Include the shared frontend style guide; optional. | Keep it inherited. | The published workspace style guide is included. |
| No checkout architecture entry. | Add a decision explaining the payment retry design. | The project decision is added alongside inherited guidance. |
A different project keeps the workspace defaults unless it publishes its own overrides.
Inspect and adjust inheritance in a project#
- Open the project’s Knowledge tab. Inherited items show their workspace origin.
- Choose Manage files to inspect an inherited entry and its available override controls.
- Use Override in project or Disable in project for an optional entry. Required entries have no project override action.
- Open View options and enable Preview session knowledge to inspect the published workspace guidance combined with your project draft.
- Save the draft, then review and publish the project changes.
Use workspace version removes a replacement override; Restore inheritance brings back a disabled entry. Review and publish those changes too. If a workspace revision changes during review, reload and check the inherited entries again before publishing.
What a session receives#
View planned changes for What a session receives. Availability depends on the released app and host versions.
Review evidence and corrections#
Knowledge assistant suggestions include source excerpts matched to the evidence used to prepare them. Open an excerpt to inspect it, and follow its source session when you have access. A matching quote establishes where the text came from; you still review whether it supports the proposed guidance.
The assistant can suggest corrections, merge equivalent entries, or retire outdated guidance. A merge keeps one entry and archives the others. Acceptance saves a draft; review and publish before new sessions use it.
Find knowledge for a task#
Search project knowledge with a task or topic to see ranked matching entries and excerpts. Agents can search their attached snapshot locally, without uploading its contents or activating settings:
ondago brain search -cwd /path/to/project -session SESSION_ID \
-query 'How should authentication validate tokens?' -limit 10Use -file snapshot.json for a downloaded packet. Results identify the snapshot, entry, excerpt lines and recorded sources. Search matches words in paths and content; it does not require an embedding service.
Continue work and plan features#
View planned changes for Continue work and plan features. Availability depends on the released app and host versions.
Review application to an agent#
Knowledge may contain agent instructions, skills, hooks, or settings. Review the destination agent’s compatibility and file changes when applying it. Downloading a snapshot alone does not activate those settings.
The project guide shows how to preview a downloaded packet. The Brain CLI reference covers explicit application, updates, and checking for local changes. An existing session’s knowledge update is a deliberate action, separate from publishing a new revision.