Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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.

Abierto
#818 4 comentarios 0 reacciones 1 asignado Ver en GitHub

@hemasekhar-p ya está trabajando en esto.

Desde el 24/2/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
Java
Estrellas
1.7k
Forks
421
Merge medio
3 d 8 h
PR fusionados (30 d)
36

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de google/adk-java

Todos los issues de google/adk-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.