Skip to content

Knowledge

How agents search reference material by meaning alongside file tools, with profile knowledge, project knowledge from Vulnesis scans, and index upkeep.

Updated 28 Oct 2026Markdown

An agent that calls Grep, Glob or Read gets its usual answer from the files, and beside it the passages from two kinds of knowledge that resemble what it asked for:

Knowledge Is Searched by
Profile knowledge The documents an agent profile lists: a handbook, a style guide, runbooks, a standards folder Workers and background agents running that profile, and a session while that agent is engaged
Project knowledge The scanner output the Vulnesis tools leave in the project’s .vulnetix directory (SARIF, CycloneDX, OpenVEX and the rest), and files you attach to a session with @ Any session in the project

Everything runs inside Belai: no embedding model to download and no service to call, so it works offline.

Keeping it current

belai agent knowledge                 # the indexes and what they hold
belai agent knowledge -index NAME     # bring the project's and NAME's indexes up to date first
belai agent knowledge -json

/knowledge in the TUI shows the same. Files an agent carries are added to its knowledge; see Importing agents.

esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.