Euisuh Jeongandbflatastic 8b7435890e fix(mcp): prevent replay after lost attached replies (#211) ...

The attached MCP backend no longer re-sends a request when its reply is lost: the app may already have applied it, so the error says the operation may have completed and to inspect the document before retrying; the next call reconnects, and a failed reconnect says the request was not sent. Fixes #194.

Also: a connection the app already closed (it drops ones idle past its socket timeout) is noticed before the next request is written and replaced then, so a pause between calls is not an error.

Co-authored-by: bflatastic <bflatastic@users.noreply.github.com>

2026-10-14 05:34:33 +07:00

..

common

M0.9: MCP server + figcraft-cli, PDF export, web app, release/CI packaging, vector edit mode, workspace lint cleanup

2026-10-09 13:31:53 -04:00

agent_tasks.rs

M4: shapes and vector behaviour suite and fixes

2026-10-12 01:32:04 +07:00

attached.rs

fix(mcp): prevent replay after lost attached replies (#211)

2026-10-14 05:34:33 +07:00

garbage.rs

M0.9: MCP server + figcraft-cli, PDF export, web app, release/CI packaging, vector edit mode, workspace lint cleanup

2026-10-09 13:31:53 -04:00

protocol.rs

fix(control): bound frames and expire queued requests (#213)

2026-10-14 05:18:40 +07:00