Asking your knowledge

When a question should be answered from your documents, Shrevix searches the knowledge base and returns ranked passages with source identifiers. The agent is instructed to use and cite those passages. Because answer formatting is model-generated, inspect the tool result and verify important claims against the source document.

Ask

In chat, just ask — the agent routes knowledge questions to knowledge search on its own:

What’s our refund SLA?

Citations

Knowledge results identify the source document for each returned passage. The agent is prompted to carry those identifiers into its answer, but the UI does not enforce one citation per claim or guarantee a clickable citation chip. Open the knowledge search result or source document when accuracy matters.

Use the Knowledge page to inspect the source and matching chunks behind an answer.

Tip

If an answer seems incomplete, open the Knowledge page and search for the topic — the most common cause is a document that was never ingested.

How it fits with code

Knowledge search runs alongside the coding tools in the same conversation: one turn can read your policy doc, then edit code to match it. Repo-scoped docs (from onboarding) and global knowledge are searched together — the transcript shows which passages were used, e.g. search knowledge — "auth token policy" → 2 passages.