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

Allow pages to send messages to agents

Abierto
  • ¿Algo no está bien?
#329 5 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript
Área
api, backend-api-design

Línea de trabajo

Read the related proposals in #31, #151, and #312, then compare their scope with the task-scoped message channel described here. The issue asks whether existing proposals can cover this interaction and raises protocol and security requirements, but names no files or tests. Done would mean deciding how the proposal fits and specifying the channel behavior and boundaries.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Could we add a standard way for a page to send messages to the visiting agent, without waiting for another tool call?

Example

A concrete example is PostHog's ask_max tool. Currently, sending a question opens the assistant UI on the page, but the assistant's answer isn't sent back to the visiting agent through the tool. The conversation continues in the page UI.

This could be a smoother experience if the visiting agent could talk directly to the site's assistant through WebMCP, receive answers and follow-up questions, and continue the conversation without having to operate the assistant's UI.

@Kulikowski explored a similar interaction in The three homes of the Agentic Web and When agents talk, with a working demo comparing WebMCP tool calls with A2A. We also discussed the missing feedback channel in Bring your own agent, coauthored with @Kulikowski and @andreban.

Strawman
  1. The visiting agent opts into messages for a specific task.
  2. The browser gives the page a channel scoped to that task.
  3. The page can send structured messages through the channel:
{
  "taskId": "analysis-123",
  "type": "question",
  "message": "Should I look at the last 7 or 30 days?"
}

The visiting agent decides whether to respond through the tool, ask the user or ignore the message. Either side can close the channel. Many websites have an in-page assistant whose logic runs on the backend. In this setup, the page relays messages between the visiting agent and the site's assistant.

Displaying messages

If the visiting agent displays a message directly, without processing it through its own LLM, the UI should clearly identify it as an unchanged message from the site's assistant. The user should be able to distinguish a relayed message from the visiting agent's own response.

Security
  • Treat messages as untrusted site content, with the same trust level as tool results.
  • Receiving a message should not grant new permissions or automatically trigger an action.
  • Replies should not expose unrelated private context.
  • The browser should enforce origin and task boundaries, rate and size limits, and close the channel when the task ends or the user leaves the page.
Relationship to A2A

A2A's task and messaging concepts could inform this without requiring sites to implement the full protocol.

Is this something the existing proposals could cover? @Kulikowski @andreban, curious how you see this fitting with those experiments.

Prior discussions
Lenguaje dominante
Bikeshed
Estrellas
4.7k
Forks
328
Merge medio
2 d 15 h
PR fusionados (30 d)
16

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 webmachinelearning/webmcp

Todos los issues de webmachinelearning/webmcp

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.