Bug
When calling adr_approve on multiple ADRs in a single parallel batch (e.g. approving 9 ADRs at once), Claude Code fires simultaneous permission prompts for each MCP tool call. The user can only interact with one prompt at a time — the remaining prompts are auto-rejected before the user can click them. This causes most approvals to silently fail.
Steps to Reproduce
- Create multiple ADRs via
adr_create
- Call
adr_approve on all of them in a single parallel batch (Claude Code dispatches MCP calls concurrently)
- Only the first 1–2 permission prompts are visible; the rest are auto-dismissed
Observed Behaviour
- First 1–2 approvals succeed
- Remaining approvals return:
The user doesn't want to proceed with this tool use (auto-rejected, no prompt shown)
- ADRs remain in
proposed status with no error message to the user
Expected Behaviour
Either:
- The tool documentation / README should explicitly warn that
adr_approve must be called sequentially (one at a time), not in parallel
- Or the MCP server could serialize approvals internally so batch approval is safe
Workaround
Call adr_approve one ADR at a time, waiting for each result before proceeding to the next:
# Safe
adr_approve("ADR-0001") # wait
adr_approve("ADR-0002") # wait
# ...
# Unsafe — causes silent rejections
[adr_approve(f"ADR-{i:04d}") for i in range(1, 10)] # parallel
Environment
- adr-kit version: 0.2.7
- Claude Code: current
- Reproducible: yes, consistently — only sequential calls succeed
Notes
This is the second packaging/integration bug found in v0.2.7. See also issue #23 (wrong config filename for setup-claude).
Bug
When calling
adr_approveon multiple ADRs in a single parallel batch (e.g. approving 9 ADRs at once), Claude Code fires simultaneous permission prompts for each MCP tool call. The user can only interact with one prompt at a time — the remaining prompts are auto-rejected before the user can click them. This causes most approvals to silently fail.Steps to Reproduce
adr_createadr_approveon all of them in a single parallel batch (Claude Code dispatches MCP calls concurrently)Observed Behaviour
The user doesn't want to proceed with this tool use(auto-rejected, no prompt shown)proposedstatus with no error message to the userExpected Behaviour
Either:
adr_approvemust be called sequentially (one at a time), not in parallelWorkaround
Call
adr_approveone ADR at a time, waiting for each result before proceeding to the next:Environment
Notes
This is the second packaging/integration bug found in v0.2.7. See also issue #23 (wrong config filename for
setup-claude).