Repository navigation
v3.4.0
What's Changed
Added
- Destructive confirmation works on protocol revision
2026-07-28(#341). That revision removed server-initiated requests mid-call, so the elicitation prompt this server has always used simply stopped working: every guarded operation on a current claude.ai client aborted withcould not confirm with the user, and no setting recovered it. Confirmation is now a two round-trip exchange on that era, unchanged on the 2025 era, chosen per call from the request itself. The summary you were shown is digested into signed state that the client echoes back, so an approval only authorises the blast radius it described — an emergency stop confirmed at 12 applications is refused rather than widened if 14 are running by the time you answer. Ten-minute expiry, fails closed,MCP_REQUEST_STATE_KEYto survive restarts. Blast-radius summaries now render in a stable order, so a reordering by Coolify cannot read as a changed blast radius and refuse an approval that was legitimately given.
Fixed
- The audit log no longer reports a failed confirmation as a human decline (#408). The refusal category was recovered by matching a substring of the error text, so a timeout, a cancelled call or a client that could not be asked all recorded as
declined. On the current protocol revision that was every destructive refusal, meaning the log answered "did someone approve this?" wrongly in exactly the case it exists for. The branch that knows why now says so, andcancelled,unavailableandstale_confirmationare distinguishable from a person saying no. - A raised confirmation is no longer audited as a successful destructive call (#341). On the two round-trip era one guarded operation writes two lines, and the first is a question. It recorded as
ok, so anything counting successful destructive operations doubled every one. It now records asawaiting_confirmation, which is worth counting in its own right. - HTTP audit lines carry the OAuth client id they always claimed to (#408). It was read from
authInfoon the handler context when the SDK hangs it offhttp.authInfo, so the field was silently absent from every line this server has ever written in HTTP mode.
Upgrading from 3.3
- Fixes a total outage of destructive operations on current clients. If
your client speaks protocol revision2026-07-28— claude.ai does today —
every guarded operation on the remote server was aborting withcould not confirm with the user, and no setting recovered it. This release is the fix.
Nothing changes for clients on the 2025 revisions, including the local stdio
server, which was never affected. - Drop-in. No required configuration.
MCP_REQUEST_STATE_KEYis optional
and only matters if you run more than one replica, or would rather a redeploy
did not interrupt someone mid-confirmation. - The audit log gained an outcome.
awaiting_confirmationmarks the first
of the two lines a guarded operation now writes on that revision. Anything
counting successful destructive calls should skip it, and anything counting
refusals should know thatdeclinednow means a person actually said no. - Blast-radius summaries are sorted. The same resources always render in
the same order. If you diff these prompts, expect a one-off reshuffle.
🖱️ One-click Claude Desktop install: download coolify-mcp.mcpb below and drag it into Settings → Extensions.