fix(core): cancel disconnected MCP interactions - #183
Conversation
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved drewstone PR — f0db1935
This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.
This approval is provisional. It rests on the audit running. If the audit cannot run — for example the CLI bridge rejects it — this approval is dismissed rather than left standing, so an unrun check never reads as a passing one.
tangletools · auto-approval · reason: drewstone_author · 2026-08-15T10:45:07Z
|
| State | Detail |
|---|---|
| Interrupted | webhook restarted |
No review verdict was produced for this run. Trigger a fresh review on the current PR head if the PR is still open.
tangletools · #183 · model: kimi-for-coding · updated 2026-08-15T11:23:37Z
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved drewstone PR — ee034684
This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.
This approval is provisional. It rests on the audit running. If the audit cannot run — for example the CLI bridge rejects it — this approval is dismissed rather than left standing, so an unrun check never reads as a passing one.
tangletools · auto-approval · reason: drewstone_author · 2026-08-15T11:24:48Z
Problem
Closing an MCP client left its pending broker request alive until timeout.
A late protocol response could replace an immediate retry.
Both attempts also reused one interaction ID, so a stale human answer could answer the retry.
Change
Proof