Repository navigation
feat(acp): bridge approval permissions - #538
Conversation
Add ACP session/request_permission handling for internal ApprovalRequest messages, map ACP outcomes back into submit_approval_response, and route agent-originated stdio JSON-RPC responses by id. Verification: - uv run pytest tests/acp -k "permission or stdio" -v - uv run pytest tests/acp -v - uv run pytest tests/cli/test_entrypoint_contract.py -k acp -v - uv run ruff check src/coding_agent/acp src/coding_agent/cli/local_runtime.py tests/acp tests/cli/test_entrypoint_contract.py
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThis PR implements ACP (Approval Context Protocol) approval bridging for Coding Agent: internal approval requests are converted into ACP ChangesACP Approval Permission Bridge
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Local review fallback because CodeRabbit remained pending with only the auto-generated review-in-progress comment. Manual P1/P2 review scope:
Result: no actionable P1/P2 findings. Verification already run locally:
|
Summary
Tests
Summary by CodeRabbit
New Features
Tests