MCP tool loses browser context between calls — Playwright MCP navigate then snapshot returns about:blank

未关闭
#42,650 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
50/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
ai-infra-agents, backend

调研方向

Start in the Dify Chatflow agent-node path that creates and destroys MCP client connections, and trace the lifecycle across successive tool invocations. Reproduce the sequence with the Playwright MCP server: browser_navigate followed by browser_snapshot or browser_take_screenshot; done means the later call retains the navigated browser context instead of returning about:blank.

由索引模型根据 Issue 内容生成。

描述

💪 enhancement
Self Checks
  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.

I'm trying to use the official Microsoft Playwright MCP Server (mcr.microsoft.com/playwright/mcp) in a Dify Chatflow to automate browser interactions — navigate to a webpage, take a screenshot, and capture the page snapshot.
However, I found that each MCP tool invocation creates a brand new MCP client connection, which is immediately destroyed after the call returns. This means the browser context (opened page, navigation state) is lost between calls. browser_navigate succeeds, but the subsequent browser_snapshot or browser_take_screenshot call opens a fresh browser context at about:blank, losing the navigated page entirely.
This makes it impossible to use any stateful MCP server (like Playwright, which maintains browser state across calls within a single session) in Dify agent nodes.

2. Additional context or comments

No response

3. Can you help us with this feature?
  • I am interested in contributing to this feature.
主要语言
TypeScript
星标
157k
派生
24.7k
平均合并
22 小时 32 分钟
30 天内合并 PR
611

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

langgenius/dify 的其他 Issue

查看 langgenius/dify 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。