Keeping the agent in-sync with the page's context
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- html
- 领域
- web-dev
调研方向
Start by reading the WebMCP specification and the surrounding discussion on this issue. The proposal covers notifying agents when page context changes and supplying page context, including optional details, but does not define an implementation or acceptance criteria. Done would require an agreed design and specification for these capabilities.
由索引模型根据 Issue 内容生成。
描述
Playing around with WebMCP, I find myself in situations where the agent is not aware of the page's context. The human user has visuals and text that help them understand what page they are on. The agent needs to use snapshots and DOM/a11y tree walking to get similar context.
Context changes can be a result of tool calls, but can also be the result of a human user interaction with the page or time-based context changes (e.g. video ended and a new one starts playing). Tool output can help provide contexts in the first case, but not others.
It might be good to enable developers with the means to:
- Let the agent know that the context has changed (due to a hard navigation, soft navigation or some other interaction).
- Provide the current page context to agents, and potentially add extra details about it.
Example use cases:
- A product page could provide high-level details about the product, allowing the agent to have more context when the user asks it basic questions about it, even before calling tools that provide more detailed descriptions.
- A checkout page with multiple different shipping addresses can provide them as context for the agent, allowing it to offer contextual shortcut enabling the user to indicate preference for one versus the other (instead of the user typing in a full address that's already on file).
- 主要语言
- Bikeshed
- 星标
- 4.7k
- 派生
- 328
- 平均合并
- 2 天 9 小时
- 30 天内合并 PR
- 15
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
webmachinelearning/webmcp 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
webmachinelearning/webmcp#362 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 72/100
webmachinelearning/webmcp#360 · 1 条评论 ·
维护者通常 1 天内回复
-
Say how an agent should weigh annotations that the page wrote about itself可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
webmachinelearning/webmcp#353 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
webmachinelearning/webmcp#343 · 1 个 reaction ·
维护者通常 1 天内回复
-
Agenda+ i18n-tracker
难度 2/5 1-3 小时 新手友好度 75/100
webmachinelearning/webmcp#273 · 3 条评论 ·
维护者通常 1 天内回复
查看 webmachinelearning/webmcp 的全部 Issue
相似的 Issue
-
good first issue
难度 2/5 1-3 小时 新手友好度 88/100
TanbirRamim/open-source-radar#353 ·
维护者通常 1 天内回复
-
copy design-review mac P3
难度 1/5 1-3 小时 新手友好度 87/100
tosunlab/hisarapp-core#509 ·
-
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复