Since a recent update, when Amazon Quick delegates a task to Kiro via ACP (Agent Client Protocol), the Kiro subshell hangs indefinitely. The approval gate prompt never appears, leaving the task spinning with no way to approve or deny the action.
Key observation: typing directly into the Kiro subshell (not initiated by Quick) works fine — the approval prompt appears as expected. The bug only manifests when Quick delegates work to Kiro via ACP.
Steps to reproduce:
In Amazon Quick, ask Quick to delegate a task to Kiro
Quick sends the task to Kiro via ACP
Kiro receives the instruction and begins execution
The approval prompt never renders — spinner continues indefinitely
Task never completes unless manually interrupted
Related GitHub issues:
kirodotdev/Kiro #6163: When invoking subagents, operation gets stuck
kirodotdev/Kiro #6235: Approval system auto-cancelling commands
Environment: Amazon Quick Desktop (latest), Kiro IDE (latest), macOS.
This effectively breaks all Quick-to-Kiro delegation workflows. Anyone found a workaround?
Just to add… this does work fine if no approval’s needed; Quick can talk to Kiro. But the moment Kiro needs to approve something, it just hangs. If I abort and paste the query in myself, then it does ask for approval.
This did work previously, but I have just noticed that it does not work in the latest version.
I’ve seen a few reports of this same behavior. The approval gate not rendering when a task is delegated via ACP seems to be a known issue in how subagent permission prompts get piped back to the parent client.
From what I have researched, one workaround that might help is adding --trust-all-tools to Kiro’s arguments in your Quick settings (Settings → Capabilities → MCP tab → Coding Agents → edit Kiro, change Arguments to acp --trust-all-tools). That bypasses the approval gate entirely so ideally speaking the task shouldn’t stall. However, the tradeoff is that it means Kiro won’t ask before executing anything, so use your judgment there.
One thing that might be worth checking is the Kiro’s ACP logs at $TMPDIR/kiro-log/kiro-chat.log on macOS as that may show what’s happening on the approval handshake side.
The same issue affects Cursor (and I checked Kiro, same result). I had to create a shim which auto approves all requests without letting Quick handle it.
Approval requests from ACP agents are definitely broken in Quick Desktop right now.
Thanks for confirming this affects Cursor as well. This appears to be a platform-level bug with how Quick Desktop handles approval requests from ACP agents. Jacob’s --trust-all-tools workaround is the only fix available right now (with the tradeoff of no approval prompts).
@Tom_Kerswill, did that workaround work for you? If you have any other questions feel free to follow up, otherwise any update within the next 3 business days would be helpful for the community.