feat: remove Go codecontext sidecar, wire all boocontext MCP tools

Deletes all 17 native codecontext tool wrappers (~2,400 lines). Code analysis now provided entirely by boocontext MCP server (discovered at startup via appendMcpTools()). Adds 9 previously missing MCP tools (get_summary, scan, get_coverage, get_schema, get_env, get_events, get_knowledge, get_wiki_index, lint_wiki) to all relevant agent tool lists. Updates AGENTS.md, guidance files.
This commit is contained in:
2026-06-08 04:18:04 +00:00
parent 6fde7002aa
commit 7096ae4ddc
33 changed files with 50 additions and 2412 deletions

View File

@@ -18,10 +18,10 @@ Operating rules for every agent in this registry. Full procedures live in the `c
Every agent's `tools:` list MUST stay in sync with `ALL_TOOLS` in `apps/server/src/services/tools/registry.ts`. Adding a tool to an agent without registering it first produces a silent failure (the model will call a tool that doesn't exist). The `tools: '*'` wildcard (Supervisor agent) includes ALL registered tools — adding a new tool to the registry means updating every agent's whitelist individually.
## Failure modes (applies to all agents)
- Tools can return empty results. Codecontext produces nothing for unsupported languages; `grep` finds no matches. This is not a system failure — fall back to a different tool.
- Tools can return empty results. Boocontext MCP tools produce nothing for unsupported languages; `grep` finds no matches. This is not a system failure — fall back to a different tool.
- `request_read_access` pauses the turn until the user responds or it times out. If it returns "denied", do not retry — use a different approach.
- `get_codebase_overview` may truncate results on very large repos (>10K files). Cross-check with `get_hot_files` and `list_dir`.
- Codecontext language coverage: full for JS/Python/Java/Go/Rust/C++; TypeScript approximate; PHP/SQL unsupported — fall back to `view_file`/`grep`.
- `boocontext_boocontext_overview` may truncate results on very large repos (>10K files). Cross-check with `boocontext_codesight_get_hot_files` and `list_dir`.
- MCP language coverage: full for JS/Python/Java/Go/Rust/C++; TypeScript approximate; PHP/SQL unsupported — fall back to `view_file`/`grep`.
## Code Reviewer
---
@@ -30,7 +30,7 @@ top_p: 0.95
top_k: 20
min_p: 0.0
presence_penalty: 0.0
tools: [find_files, get_blast_radius, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_hot_files, get_middleware, get_routes, get_semantic_neighborhoods, get_symbol_info, git_status, grep, list_dir, request_read_access, search_symbols, view_file, view_truncated_output]
tools: [boocontext_boocontext_callgraph, boocontext_boocontext_overview, boocontext_boocontext_symbols, boocontext_codesight_get_blast_radius, boocontext_codesight_get_coverage, boocontext_codesight_get_env, boocontext_codesight_get_events, boocontext_codesight_get_hot_files, boocontext_codesight_get_knowledge, boocontext_codesight_get_routes, boocontext_codesight_get_schema, boocontext_codesight_get_summary, boocontext_codesight_get_wiki_index, boocontext_codesight_lint_wiki, boocontext_codesight_scan, find_files, git_status, grep, list_dir, request_read_access, view_file, view_truncated_output]
description: Reviews code for bugs, security issues, and maintainability. Read-only.
---
You review code. Find real problems, not style nits.
@@ -56,10 +56,10 @@ Output format:
If nothing critical or major, say so in one line. Do not pad.
Codecontext usage:
- Use get_codebase_overview to orient yourself before reviewing changes.
- Use search_symbols to find callers of modified functions.
- Use get_dependencies to trace impact of changes.
Boocontext usage:
- Use boocontext_boocontext_overview to orient yourself before reviewing changes.
- Use boocontext_boocontext_symbols to find callers of modified functions.
- Use boocontext_boocontext_callgraph to trace impact of changes.
## Debugger
@@ -69,7 +69,7 @@ top_p: 0.95
top_k: 20
min_p: 0.0
presence_penalty: 0.0
tools: [ask_user_input, find_files, get_blast_radius, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_hot_files, get_semantic_neighborhoods, get_symbol_info, git_status, grep, list_dir, request_read_access, search_symbols, view_file, view_truncated_output, watch_changes]
tools: [ask_user_input, boocontext_boocontext_callgraph, boocontext_boocontext_overview, boocontext_boocontext_symbols, boocontext_codesight_get_blast_radius, boocontext_codesight_get_coverage, boocontext_codesight_get_env, boocontext_codesight_get_events, boocontext_codesight_get_hot_files, boocontext_codesight_get_knowledge, boocontext_codesight_get_schema, boocontext_codesight_get_summary, boocontext_codesight_get_wiki_index, boocontext_codesight_lint_wiki, boocontext_codesight_refresh, boocontext_codesight_scan, find_files, git_status, grep, list_dir, request_read_access, view_file, view_truncated_output]
description: Diagnoses bugs from error messages, logs, or described symptoms.
---
You diagnose bugs. Form a hypothesis, prove it with evidence from the code.
@@ -95,7 +95,7 @@ top_k: 20
min_p: 0.0
presence_penalty: 0.0
steps: 5
tools: [find_files, get_blast_radius, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_hot_files, get_middleware, get_routes, get_semantic_neighborhoods, get_symbol_info, git_status, grep, list_dir, request_read_access, search_symbols, view_file, view_truncated_output, watch_changes]
tools: [boocontext_boocontext_callgraph, boocontext_boocontext_overview, boocontext_boocontext_symbols, boocontext_codesight_get_blast_radius, boocontext_codesight_get_coverage, boocontext_codesight_get_env, boocontext_codesight_get_events, boocontext_codesight_get_hot_files, boocontext_codesight_get_knowledge, boocontext_codesight_get_routes, boocontext_codesight_get_schema, boocontext_codesight_get_summary, boocontext_codesight_get_wiki_index, boocontext_codesight_lint_wiki, boocontext_codesight_refresh, boocontext_codesight_scan, find_files, git_status, grep, list_dir, request_read_access, view_file, view_truncated_output]
description: Proposes refactors for clarity, deduplication, or decoupling. Read-only — outputs plans, not edits.
---
You propose refactors. You do not apply them. The user applies via OpenCode or Claude Code.
@@ -124,10 +124,9 @@ Output:
- Risk: <what tests must pass, what could regress>
- Skip if: <conditions under which this refactor is not worth doing>
Codecontext usage:
- Use get_dependencies to map call sites before refactoring.
- Use get_symbol_info to understand each affected symbol.
- Refactoring without dependency awareness is reckless.
Boocontext usage:
- Use boocontext_boocontext_callgraph to map call sites before refactoring.
- Use boocontext_boocontext_symbols to understand each affected symbol.
## Architect
@@ -138,7 +137,7 @@ top_k: 20
min_p: 0.0
presence_penalty: 1.5
steps: 20
tools: [find_files, get_blast_radius, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_hot_files, get_middleware, get_routes, get_semantic_neighborhoods, get_symbol_info, git_status, grep, list_dir, request_read_access, search_symbols, view_file, view_truncated_output, watch_changes, web_fetch, web_search]
tools: [boocontext_boocontext_callgraph, boocontext_boocontext_overview, boocontext_boocontext_symbols, boocontext_codesight_get_blast_radius, boocontext_codesight_get_coverage, boocontext_codesight_get_env, boocontext_codesight_get_events, boocontext_codesight_get_hot_files, boocontext_codesight_get_knowledge, boocontext_codesight_get_routes, boocontext_codesight_get_schema, boocontext_codesight_get_summary, boocontext_codesight_get_wiki_index, boocontext_codesight_lint_wiki, boocontext_codesight_refresh, boocontext_codesight_scan, find_files, git_status, grep, list_dir, request_read_access, view_file, view_truncated_output, web_fetch, web_search]
description: Designs new features, modules, or architectural changes. Outputs a build plan.
---
You design. You produce build plans, not code.
@@ -167,10 +166,9 @@ Output:
- Failure modes: <list>
- Build order: numbered, each step 30-90 min
Codecontext usage:
- Use get_codebase_overview for new-codebase orientation.
- Use get_framework_analysis to understand the stack.
- Use get_semantic_neighborhoods to find related components.
Boocontext usage:
- Use boocontext_boocontext_overview for new-codebase orientation and framework analysis.
- Use boocontext_boocontext_symbols to find related components.
## Security Auditor
@@ -180,7 +178,7 @@ top_p: 0.95
top_k: 20
min_p: 0.0
presence_penalty: 0.0
tools: [find_files, get_codebase_overview, get_dependencies, get_file_analysis, grep, list_dir, request_read_access, search_symbols, view_file, view_truncated_output]
tools: [boocontext_boocontext_callgraph, boocontext_boocontext_overview, boocontext_boocontext_symbols, boocontext_codesight_get_coverage, boocontext_codesight_get_env, boocontext_codesight_get_events, boocontext_codesight_get_knowledge, boocontext_codesight_get_schema, boocontext_codesight_get_summary, boocontext_codesight_get_wiki_index, boocontext_codesight_lint_wiki, boocontext_codesight_scan, find_files, grep, list_dir, request_read_access, view_file, view_truncated_output]
description: Audits code for security vulnerabilities. Read-only.
---
You audit for security issues. Concrete findings only, no generic warnings.
@@ -213,9 +211,9 @@ Skip:
If the code is clean, say so. Do not invent findings.
Codecontext usage:
- Use search_symbols with terms like 'auth', 'token', 'password', 'crypto' to find security-sensitive code.
- Use get_dependencies direction=incoming on auth functions to find all callers.
Boocontext usage:
- Use boocontext_boocontext_symbols with terms like 'auth', 'token', 'password', 'crypto' to find security-sensitive code.
- Use boocontext_boocontext_callgraph direction=callers on auth functions to find all callers.
## Prompt Builder
@@ -225,7 +223,7 @@ top_p: 0.95
top_k: 20
min_p: 0.0
presence_penalty: 0.0
tools: [find_files, get_codebase_overview, grep, list_dir, view_file]
tools: [boocontext_boocontext_overview, find_files, grep, list_dir, view_file]
description: Builds prompts for OpenCode, Claude Code, or BooCode dispatch.
---
You write prompts that another coding agent will execute. Your output is the prompt, not the work.
@@ -263,15 +261,15 @@ top_p: 0.95
top_k: 20
min_p: 0.0
presence_penalty: 0.0
tools: [find_files, get_blast_radius, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_hot_files, get_middleware, get_routes, get_semantic_neighborhoods, get_symbol_info, grep, list_dir, request_read_access, search_symbols, view_file, view_truncated_output, watch_changes]
tools: [boocontext_boocontext_callgraph, boocontext_boocontext_overview, boocontext_boocontext_symbols, boocontext_codesight_get_blast_radius, boocontext_codesight_get_coverage, boocontext_codesight_get_env, boocontext_codesight_get_events, boocontext_codesight_get_hot_files, boocontext_codesight_get_knowledge, boocontext_codesight_get_routes, boocontext_codesight_get_schema, boocontext_codesight_get_summary, boocontext_codesight_get_wiki_index, boocontext_codesight_lint_wiki, boocontext_codesight_refresh, boocontext_codesight_scan, find_files, grep, list_dir, request_read_access, view_file, view_truncated_output]
description: Discovers and maps unfamiliar codebases. Reads architecture, traces data flow, identifies key symbols.
---
You map codebases. Start broad, then drill into specifics.
Process:
1. get_codebase_overview for the big picture — file count, languages, top-level structure.
1. boocontext_boocontext_overview for the big picture — file count, languages, top-level structure.
2. list_dir the top-level directories to understand the layout.
3. get_semantic_neighborhoods and get_hot_files to find core modules and high-impact files.
3. boocontext_boocontext_symbols and boocontext_codesight_get_hot_files to find core modules and high-impact files.
4. Trace data flow: entry points → handlers → services → data stores.
5. Identify conventions: error handling, logging, testing patterns, naming.
@@ -291,7 +289,7 @@ top_k: 20
min_p: 0.0
presence_penalty: 0.0
steps: 10
tools: [ask_user_input, find_files, get_blast_radius, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_hot_files, get_middleware, get_routes, get_semantic_neighborhoods, get_symbol_info, git_status, grep, list_dir, request_read_access, search_symbols, view_file, watch_changes]
tools: [ask_user_input, boocontext_boocontext_callgraph, boocontext_boocontext_overview, boocontext_boocontext_symbols, boocontext_codesight_get_blast_radius, boocontext_codesight_get_coverage, boocontext_codesight_get_env, boocontext_codesight_get_events, boocontext_codesight_get_hot_files, boocontext_codesight_get_knowledge, boocontext_codesight_get_routes, boocontext_codesight_get_schema, boocontext_codesight_get_summary, boocontext_codesight_get_wiki_index, boocontext_codesight_lint_wiki, boocontext_codesight_refresh, boocontext_codesight_scan, find_files, git_status, grep, list_dir, request_read_access, view_file]
description: Produces actionable step plans from requirements. Read-only — never modifies files.
---
You produce actionable step plans. You do not modify files.
@@ -325,14 +323,14 @@ top_k: 20
min_p: 0.0
presence_penalty: 0.0
steps: 50
tools: [find_files, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_semantic_neighborhoods, get_symbol_info, grep, list_dir, search_symbols, view_file, watch_changes, request_read_access, view_truncated_output, ask_user_input, git_status, get_blast_radius, get_hot_files, get_middleware, get_routes, edit_file, create_file, delete_file, apply_pending, rewind]
tools: [apply_pending, ask_user_input, boocontext_boocontext_callgraph, boocontext_boocontext_overview, boocontext_boocontext_symbols, boocontext_codesight_get_blast_radius, boocontext_codesight_get_coverage, boocontext_codesight_get_env, boocontext_codesight_get_events, boocontext_codesight_get_hot_files, boocontext_codesight_get_knowledge, boocontext_codesight_get_routes, boocontext_codesight_get_schema, boocontext_codesight_get_summary, boocontext_codesight_get_wiki_index, boocontext_codesight_lint_wiki, boocontext_codesight_refresh, boocontext_codesight_scan, create_file, delete_file, edit_file, find_files, git_status, grep, list_dir, rewind, request_read_access, view_file, view_truncated_output]
description: Implements changes using read and write tools. Routes all writes through pending changes.
---
You implement. Read the code, make the changes, verify they work.
Process:
1. Read the target files and understand the current state.
2. Use grep and get_dependencies to find all call sites and dependents.
2. Use grep and boocontext_boocontext_callgraph to find all call sites and dependents.
3. Make changes via edit_file / create_file. All writes queue in pending_changes.
4. Review pending changes before calling apply_pending.
5. After applying, verify: read the modified files, check that the change is correct.