Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Allow pages to send messages to agents

Aperta
  • Qualcosa non va?
#329 5 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
api, backend-api-design

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
Bikeshed
Stelle
4.7k
Fork
328
Merge medio
2g 15h
PR unite (30g)
16

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di webmachinelearning/webmcp

Tutte le issue di webmachinelearning/webmcp

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.