Reviewer chat with real MCP tool parity.
This surface now speaks to the live template-review MCP lane. Reads run inline, writes stop for explicit approval, and reviewer threads persist server-side so the flow supports real parallel work instead of a debug shell.
Loading lane…
Fetching live runtime config.
...
Live tools exposed through chat
The app uses the runtime tool catalog instead of a static demo list.
0
Shared reviewer threads
Threads persist through the server store so reviewers can reopen work across tabs and recover on another machine.
Live reviewer workflow
The UI reads the real MCP catalog on load instead of relying on scaffolded demo data.
Queue, version, asset, metrics, release, and field-map reads can be executed from natural language.
Reviewer-safe writes are available from chat, but every mutation is surfaced for explicit approval first.
Multiple review threads can stay active at once, with per-thread turn locks and record-level write claims to prevent collisions.