Problem
Currently, there is no option to provide a link to project-specific documentation. As a result, the agent only relies on its general knowledge, which may lead to inaccuracies or incomplete answers in the context of a particular system/project.
What problem does this solve?
It allows the agent to rely on the most up-to-date and authoritative project documentation, ensuring precise and project-specific answers.
Solution
Add support for specifying a documentation URL (e.g., in the agent configuration or prompt). The agent should then use the documentation available at this link as its main knowledge source.
How should it work?
-
The user provides a URL to their project’s documentation (e.g., Docusaurus, internal GitHub Pages, Confluence, etc.).
-
The agent indexes or queries the content directly.
-
The agent prioritizes knowledge from this documentation when generating responses.
Use Case
-
When working with an API and needing reference to the latest project-specific docs.
-
For internal company projects that have custom documentation.
-
Onboarding new developers — the agent can act as an interactive guide to the project’s docs.
Priority
Medium - Important improvement
Additional Info
It should be possible to provide a URL to the project’s own documentation (e.g., hosted with Docusaurus or similar tools). This way, the agent always refers to the correct and most relevant knowledge base.