The control server gave up after 60 s with "timeout" but left the request queued, so the app ran it later and a client retry applied it twice. Requests now carry a shared state: on timeout the server cancels a request the app has not started (reply state "not-run", safe to retry) and the app skips it; one already started replies state "may-have-run". The MCP bridge passes that on in its error. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| cadcraft | ||
| cadcraft-cli | ||
| cadcraft-web | ||