Subagent with K8s MCP server hangs after upgrading kiro

Checks

• I have run q doctor in the affected terminal session
• I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
• I have run q restart and replicated the issue again

Operating system

macOS 26.3.0

Expected behaviour

Subagents configured with K8s MCP tooling should function correctly after upgrading Kiro-CLI to 1.29.1, just as they did previously.
The K8s-powered agent should work both as a subagent and when invoked directly.

Actual behaviour

After upgrading to 1.29.1, subagents using the K8s MCP tooling hang with no response.
However, when the K8s-powered agent is invoked directly (kiro-cli --agent k8s), it works as expected.

Steps to reproduce

1. Configure a subagent with K8s MCP tooling.
2. Upgrade Kiro-CLI to version 1.29.1.
3. Invoke the K8s-powered subagent.
4. Observe that the subagent hangs with no response.

Environment

<This will be visible to anyone. Do not include personal or sensitive information>

[q-details]
version = "1.29.1"
hash = "b38a4a5326a279f54908508508053d716c45afcf"
date = "2026-04-03T05:55:40.77818Z (5h ago)"
variant = "full"

[system-info]
os = "macOS 26.3.0 (25D125)"
chip = "Apple M3 Pro"
total-cores = 12
memory = "18.00 GB"

[environment]
cwd = "/Volumes/Work/projects/test"
cli-path = "/Volumes/Work/projects/test"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "iTerm 2"
install-method = "unknown"

Riproduci il blocco con il subagent K8s MCP dopo l’aggiornamento a Kiro-CLI 1.29.1, quindi confrontalo con l’invocazione diretta funzionante tramite kiro-cli --agent k8s. Traccia l’invocazione del subagent e l’integrazione degli strumenti MCP; l’issue è completata quando l’agente basato su K8s risponde correttamente sia come subagent sia quando viene invocato direttamente.