[建议 / Feature] Sub-agents can use the built-in browser.

提交前确认 · Pre-submission checklist

• 我已搜索过现有 issue，确认这不是重复提议 / I searched existing issues and confirmed this isn't a duplicate.
• 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.

问题类别 · Category

工具调用 / MCP · Tool use / MCP

涉及的 Agent 框架 · Agent framework

ZCode Agent（自研）

使用场景 · Use case

I created a QA sub-agent dedicated to testing. However, it currently cannot use the built-in browser because runtime_scope === "subagent" restricts sub-agents from accessing it. To work around this, I applied a temporary local patch to my machine and verified that it runs successfully. Using the built-in browser is significantly faster compared to using the MCP Chrome Playwright setup, which runs quite slowly. Please consider optimizing and applying a permanent patch in the upcoming releases so that sub-agents can utilize the built-in browser natively for better performance.

建议方案 · Proposal

Modify the permission logic for runtime_scope === "subagent" to allow sub-agents to access the built-in browser. Alternatively, introduce a new configuration flag, such as allow_subagent_browser: true, so users can explicitly enable this feature when creating specialized testing or QA sub-agents. This will maintain system security while unlocking high-performance browser automation.

预期价值 · Expected value

Sub-agents should be able to launch and interact with the built-in browser without being blocked by the runtime scope restriction. When running browser automation tasks, the system should execute them directly through the built-in browser instead of forcing a fallback to external tools like MCP Chrome Playwright.

你认为的优先级 · Your perceived priority

中 · Medium

你使用的 ZCode 版本 / 环境 · ZCode version / environment

v3.10.1

补充材料 · Additional context

No response

Start by locating the permission logic for runtime_scope === "subagent" and the built-in browser entry point. Compare the current restriction with the proposed allow_subagent_browser configuration, then verify that a QA sub-agent can launch and interact with the built-in browser without falling back to MCP Chrome Playwright.