Frontmatter
| id | 9180 |
| title | Promote ask_knowledge_base as RAG Sub-Agent in AGENTS_STARTUP.md |
| state | Closed |
| labels | documentationenhancementai |
| assignees | tobiu |
| createdAt | Feb 16, 2026, 3:42 AM |
| updatedAt | Feb 16, 2026, 3:45 AM |
| githubUrl | https://github.com/neomjs/neo/issues/9180 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Feb 16, 2026, 3:45 AM |
Promote ask_knowledge_base as RAG Sub-Agent in AGENTS_STARTUP.md

tobiu
Feb 16, 2026, 3:44 AM
Input from Gemini 3 Pro:
✦ I have updated
AGENTS_STARTUP.mdto include the "Ask the Expert" Protocol.This new section (3.4) explicitly mandates the use of
ask_knowledge_baseas a RAG Sub-Agent for verifying syntax before writing code, specifically targeting "hallucination hazards" like outdated binding syntax.The documentation now clearly defines the tool's role as the single source of truth for framework patterns.
tobiu assigned to @tobiu on Feb 16, 2026, 3:44 AM
tobiu closed this issue on Feb 16, 2026, 3:45 AM
We need to update
AGENTS_STARTUP.mdto explicitly promote theask_knowledge_basetool as a RAG Sub-Agent.Problem: Agents (including Gemini) often rely on outdated training data for framework-specific syntax (e.g., State Provider bindings, Config system), leading to "hallucinated" legacy code. They underestimate the power of
ask_knowledge_base, viewing it as a simple search rather than a grounded expert.Solution: Refactor
AGENTS_STARTUP.mdto include a new "Ask the Expert" Protocol.ask_knowledge_baseas an "Embedded RAG Sub-Agent" that has read-access to the current repository state.ask_knowledge_base(query='current syntax for state provider bindings')ask_knowledge_base(query='how to implement a reactive config')This will shift agent behavior from "guessing based on training" to "verifying against the repo".