Knowledge base
Project knowledge types, items, revision history, and agent-readable memory.
Knowledge base
The knowledge base stores durable project memory outside ticket comments and agent runs — decisions, ideas, open questions, constraints, and custom types your project defines.
Why it exists
Tickets capture work in motion. Knowledge items capture what the team wants to remember: product decisions, architectural constraints, research notes, and open questions that may later resolve into tickets.
Agents and chat can search and read knowledge during runs when MCP tools are enabled. Humans browse and edit knowledge in the project UI.
Knowledge types
Each item belongs to a type (for example Idea, Decision, Open Question, Constraint). Types define:
- Allowed statuses and defaults
- Whether items can be pinned for chat context
- Mutation mode — auto-approve (agents apply immediately) or approval required (proposals inbox)
- Guidance text shown to agents
Global types ship in content modules and default to auto-approve. Project-local types are created by project admins. Projects enable global types by installing modules that include them.
Items, history, and proposals
Members create and edit knowledge items with markdown bodies (including references to tickets and docs). Every change is recorded in revision history with diffs and restore — the same underlying system as Configuration revision history.
Browse Recent changes at Knowledge → Recent changes, or open an item's History tab for the full timeline.
On approval-required types, proposals from chat or agents create or update items only after a human approves them in the project Proposals inbox. On auto-approve types, authorized agent changes apply immediately.
Stale-write protection
Updates on auto-approve types require expectedRevision. If another change landed first, the write declines with stale_revision and the current revision number — retry after refreshing the item.
Ticket knowledge activity
Ticket detail can show a Knowledge activity block linking recent knowledge items referenced in ticket context. See Tickets.
Setup & configuration
- Browse knowledge at Project → Knowledge (under Data in the sidebar)
- View Recent changes at Knowledge → Recent changes
- Manage project-local types at Settings → Knowledge types
- Superadmins manage global types at Platform → Knowledge types
- Install content modules that bundle knowledge types when you want shared templates across projects
Agents read knowledge via MCP tools (search_knowledge_items, get_knowledge_item, list_pinned_knowledge, list_knowledge_item_revisions) when allowed on the agent configuration.