Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

When multiple agents communicate via the A2A protocol, the invocationContext.session.state is not transformed and transmitted to the message, and SSE streaming is not supported.

Open
#818 4 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@hemasekhar-p is already working on this.

Since Feb 24, 2026.

Assessment

This issue has not been assessed yet.

Description

needs review

** Please make sure you read the contribution guide and file the issues in the right place. **
Contribution guide.

Is your feature request related to a specific problem?

1.Based on the following source code reading, in the logic of converting invocationContext to Message using EventConverter.convertEventsToA2AMessage:

Optional<Message> a2aMessageOpt = com.google.adk.a2a.EventConverter.convertEventsToA2AMessage(invocationContext);

Image

metadata is not assigned. Therefore, will the following code always return a null case:

Map<String, Object> metadata = originalMessage.getMetadata() == null ? Map.of() : originalMessage.getMetadata();

Is it possible to convert invocationContext.session.state to the metadata of the Message, as additional information in the communication protocol between the client agent and the server agent? like this:

Image 2.Multiple agents communicate via the A2A protocol, using a synchronous blocking approach. Image

Due to the time-consuming nature of this communication, which negatively impacts user experience, it is recommended to replace the synchronous approach with SSE streaming output. Simultaneously, the client should use a pre-implemented streaming HTTP request to establish connections.

Image
Describe the Solution You'd Like

Some of the solution code logic is above.

Dominant language
Java
Stars
1.7k
Forks
433
Avg merge
3d 11h
Merged PRs (30d)
50

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/adk-java

All issues in google/adk-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.