Context Compression and agents/config in ADK GO

[dimetron]

Are there any plans to bring the ADK Python feature set into alignment with ADK Go?

In particular, I’m interested in:
• Context / compaction:
https://google.github.io/adk-docs/context/compaction/
• Agents / config:
https://google.github.io/adk-docs/agents/config/

It would be great to understand whether feature parity is on the roadmap, and if so, what the expected timeline might look like.

Appreciate any insights you can share.

[aniruddhaadak80]

Feature parity questions like this matter more in Go than people sometimes admit, because missing memory or config primitives change the architecture you build around the SDK, not just the ergonomics.nnEven a rough roadmap would help here. If compaction and declarative agent config are planned, teams can avoid building temporary abstractions that will be thrown away later. If they are intentionally out of scope for adk-go, that is also useful to know early.

[karolpiotrowicz]

Thanks for the question -- good news on one front:

Agent Config is already supported in ADK Go as of v0.3.0. You can use YAML-based agent definitions with adk run, adk web, or load them programmatically. See the Agent Config docs (Go is listed as a supported SDK).

For Context Compaction -- this is on our roadmap for ADK Go. We've heard this feedback from multiple users and understand the impact - we're actively working on sharing a public roadmap for better transparency on timelines, which will be available soon.