chore: sync local changes, add Chinese docs and opencode config
This commit is contained in:
@@ -612,6 +612,31 @@ code-review-graph embed --provider voyage --model voyage-code-3
|
||||
> and `--embedding-model`; cloud choices may transmit this source-derived text
|
||||
> and incur API cost.
|
||||
|
||||
#### Progress Notifications & Timeouts
|
||||
|
||||
Long-running tools (`coverage_tool`, `deep_read_plan_tool`, `score_review_tool`,
|
||||
`detect_changes_tool`) run their work in a worker thread while the MCP event
|
||||
loop periodically emits `notifications/progress` (default every 15s). MCP
|
||||
clients such as opencode that set `resetTimeoutOnProgress` therefore never hit
|
||||
the default 60s request timeout, even on repositories with hundreds of files.
|
||||
The engine also accepts an optional `progress_cb` callback for real per-file /
|
||||
per-metric progress; clients that do not request a progress token are unaffected
|
||||
(notifications are skipped silently).
|
||||
|
||||
As a server-side backstop, `CRG_TOOL_TIMEOUT` (seconds) bounds these tools and
|
||||
returns a readable error instead of letting the client time out. On the client
|
||||
side you can also raise the MCP request timeout, e.g. in opencode:
|
||||
|
||||
```jsonc
|
||||
"mcp": {
|
||||
"code-review-graph": {
|
||||
"type": "local",
|
||||
"command": ["...", "serve", "--repo", "/path/to/repo"],
|
||||
"timeout": 600000
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
#### Tool Filtering
|
||||
|
||||
CRG exposes 31 MCP tools by default. In token-constrained environments, you can
|
||||
|
||||
Reference in New Issue
Block a user