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

Reposition feature as a generic communication tool?

Abierto
  • ¿Algo no está bien?
#236 10 comentarios 6 reacciones 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, web-dev
Área
api

Línea de trabajo

Start by reading the WebMCP spec and explainers mentioned in the issue, then review the discussion for prior decisions. The proposal explores exposing functions across environments, origins, WebDriver, and service workers, with browser and LLM integrations. Done would require agreeing on scope and a design before implementation.

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

Descripción

I only read through the spec and explainers on a plane, so apologies if this is stuff that's already been discussed.

I wonder if it would be better to reposition this idea as a general way to call functions in other environments.

Right now, it's a pain in the arse to do simple function calls between environments (windows, workers, etc). So much so, that there are popular libraries to try and make it easier.

When I was looking at the API, I thought "haha I could totally abuse this to be like a built-in comlink", but then I thought "maybe it doesn't have to be an abuse".

Let's say the whole tool registering thing is just a way for one environment to expose function calls to another. Then, add in the ability to expose particular functions to particular other origins. There's your comlink.

Then, add in the ability to expose particular functions to "the browser" - this would make the function available via WebDriver, and whatever tooling the browser chooses to provide. This is where the schema and description comes in. This means the browser could expose this functionality via its own interface, and build a form for the parameters. Or, sure, an LLM could do all that transparently. I think it might be an easier sell like this - the LLM capability just falls out of the other capabilities provided.

Developers could simply use this as an easier way to call functions in a worker - nothing to do with LLMs. Or they could do it to expose site functionality to the outside world.

A service worker could register functions at install time, meaning these things can be callable without a window open. They may choose to open a window (or interact with another window). All they'd be doing is calling (probably private) tools on the window. With some feature that allows a tool to return "don't return until I've navigated and the next page is dom-ready" - now you have a single public tool in a service worker that can perform MPA automations.

Just don't call it Web Intents I guess.

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.