QA_source_index

To find relevant documentation for multi-agent configuration, this tool maps keywords from your question to official docs sections and source code entry points like `src/qwenpaw/agents/`. It classifies the topic and instantly returns the correct file paths.

Locating source code entry points for CLI and memory features is done by mapping your query keywords to local repository structures. It identifies and suggests exact paths like `src/qwenpaw/cli/` and related memory directories for immediate reference.

Yes, you can route installation questions to specific markdown files by classifying the query against topic keywords. The system targets `website/public/docs/<topic>.<lang>.md` files to pinpoint the exact installation documentation you need.

No external dependencies are required. The tool relies entirely on the local repository structure and official documentation files to identify candidate paths and route user questions to the correct locations.

The best way to reference docs and code paths for skills and MCP topics is using the built-in QA workflow. It prefetches relevant documentation pages and source locations based on keyword classification, reducing search friction and answer latency.

You should avoid keyword-based question routing if your query lacks specific topic keywords like installation, configuration, or CLI. Without recognizable terms, the system cannot reliably classify the intent to map the question to the correct source paths.