Reliability

A human approval becomes a single-use capability bound to one Claude Code operation, and the tool gateway rejects any replay after redemption

Treat Claude Code approval as a single-use capability

A human approval should authorize one exact Claude Code effect, not every retry that follows. Issue a single-use capability and record its redemption at the tool gateway.

An effect ledger records completed, failed, and pending MCP steps, then selects resume, compensate, or stop based on verified production state

Recover a partially completed Claude Code MCP workflow

A multi-step Claude Code run can fail after several external writes have already succeeded. Use an effect ledger to resume, compensate, or stop without repeating completed work.

Stopping Claude Code does not cancel queued MCP work

A stopped Claude Code run can leave queued MCP calls and provider jobs alive. Use a cancellation barrier to revoke authority, drain pending work, and prove the run is quiet.

A timed-out Claude Code MCP write enters an unknown state, checks an operation journal, and either verifies the existing effect or retries with the same idempotency key

Treat a timed-out MCP write as an unknown outcome

A timed-out MCP write may have failed, succeeded, or finished after the client gave up. Use an operation journal and effect lookup before Claude Code retries it.