-
Notifications
You must be signed in to change notification settings - Fork 418
Description
📋 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)
Multiple services / System-wide issue
🚦 Impact/Severity
Minor inconvenience
🐛 Bug Description
When using Agents that rely on A2A Tools, the agents repeatedly emit warnings like so:
UserWarning: [EXPERIMENTAL] RemoteA2aAgent: ADK Implementation for A2A support (A2aAgentExecutor, RemoteA2aAgent and corresponding supporting components etc.) is in experimental mode and is subjected to breaking changes. A2A protocol and SDK are themselves not experimental. Once it's stable enough the experimental mode will be removed. Your feedback is welcome.
This warning appears continuously during runtime and floods the logs.
🔄 Steps To Reproduce
- Create 2 agents with A2A tools.
- Observe logs during agent interactions.
🤔 Expected Behavior
No repeated experimental mode warnings.
📱 Actual Behavior
Multiple logs are generated with the experimental mode warning for every relevant A2A operation.
💻 Environment
- Kubeadm cluster version 1.34
- kagent version 0.7.18
🔧 CLI Bug Report
No response
🔍 Additional Context
No response
📋 Logs
UserWarning: [EXPERIMENTAL] RemoteA2aAgent: ADK Implementation for A2A support (A2aAgentExecutor, RemoteA2aAgent and corresponding supporting components etc.) is in experimental mode and is subjected to breaking changes. A2A protocol and SDK are themselves not experimental. Once it's stable enough the experimental mode will be removed. Your feedback is welcome.📷 Screenshots
No response
🙋 Are you willing to contribute?
- I am willing to submit a PR to fix this issue
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Backlog