[BUG] kagent 100% CPU and not responding well to queries

[LutzLange]

📋 Prerequisites

• I have searched the existing issues to avoid creating a duplicate
• By submitting this issue, you agree to follow our Code of Conduct
• I am using the latest version of the software
• I have tried to clear cache/cookies or used incognito mode (if ui-related)
• I can consistently reproduce this issue

🎯 Affected Service(s)

Not Sure

🚦 Impact/Severity

Blocker

🐛 Bug Description

I'm trying out kagent with subagents.

I've created a new agent and added k8s-agent and helm-agent as resources.
I did remove the doc-query tool from booth agents before doing this. I've asked my new agent to list pods running on my kubernetes cluster.

I can see the call to the to k8s_agent and a response, but I don't get a text response.
The k8s-agent pod goes to 100% CPU.

Here is the UI:

🔄 Steps To Reproduce

I'm running on a kind cluster on my Ubuntu 24.04.

I've used this guide for setup.

🤔 Expected Behavior

I should get a text response with the running pods.
k8s-agent pod should not eat away CPU cycles at 100% after one call.

📱 Actual Behavior

No response

💻 Environment

Ubuntu 24.04 LTS
Kind Cluster 1.34.0
Kagent 0.6.12

Kagent Debug:

[LutzLange]

Kagent Debug:

versions.txt
promql-agent-db6896bb7-cmc4z-kagent-logs.txt
observability-agent-7c85654ffb-6bnwd-kagent-logs.txt
my-agent-c55978bc8-hj8qm-kagent-logs.txt
kgateway-agent-597bf79b67-kgrqz-kagent-logs.txt
kagent-ui-7bf7fcfcff-jwz25-ui-logs.txt
kagent-tools-84987689b9-qzrtb-tools-logs.txt
kagent-querydoc-6d669b748-s7ndr-querydoc-logs.txt
kagent-grafana-mcp-5bb8d7d56d-qn6h9-grafana-mcp-logs.txt
kagent-controller-7bf468f5df-ppmlv-controller-logs.txt
k8s-agent-594494dd6f-mg7bf-kagent-logs.txt
istio-agent-76f7d8df6f-752gw-kagent-logs.txt
helm-agent-7d8fd777c6-m2rlt-kagent-logs.txt
cilium-policy-agent-58686467bb-w5hd9-kagent-logs.txt
cilium-manager-agent-688c4fcc9f-x8tcm-kagent-logs.txt
cilium-debug-agent-68984cbddf-8g4vq-kagent-logs.txt
argo-rollouts-conversion-agent-6989b779c-hd666-kagent-logs.txt
secrets.txt

[LutzLange]

@peterj could you take a look?

[peterj]

I was able to reproduce this -- the first issue you mention with the output being in json -- that's already fixed. However, the second one is still there.

It also happens with a single agent, sending a single query to it.