fix: move built-in browser to direct model tools

Browser control was grouped with client PC control even though it operates GoodBuddy's isolated browser. It now appears as Built-in Browser under direct-model tools with its existing master switch, profiles, and diagnostics, while Computer Control only lists capabilities that act on the client PC.

The existing capability ID and saved state are preserved. Enabling the browser lets direct models use it in Execute mode without per-action prompts.

Release note: 将内置浏览器移至直连模型工具,并明确它不会控制客户端已安装的浏览器;原有开关状态保持不变。
This commit is contained in:
mesalogo
2026-08-18 11:24:09 +08:00
parent 5dddccb282
commit 7a46422fc1
14 changed files with 271 additions and 87 deletions
@@ -41,6 +41,9 @@ describe('computer capability catalog', () => {
new Set(['managed-linux-desktop-driver'])
)
).toBe(true)
expect(browser.name).toBe('内置浏览器')
expect(browser.description).toContain('不会控制客户端已安装的浏览器')
expect(browser.riskSummary).toContain('不再逐次询问')
expect(desktop.description).toContain('技术预览')
expect(desktop.riskSummary).toContain('尚未')
})
@@ -34,9 +34,9 @@ export const computerCapabilityCatalog: readonly ComputerCapabilityCatalogEntry[
Object.freeze([
Object.freeze({
id: 'host-browser-control',
name: '浏览器控制',
name: '内置浏览器',
description:
'使用临时隔离会话执行网页操作;命名配置当前仅保存未来托管隔离所需的元数据。',
'使用 GoodBuddy 内置的临时隔离浏览器执行网页操作,不会控制客户端已安装的浏览器;命名配置当前仅保存未来托管隔离所需的元数据。',
enabledByDefault: false,
implementationKind: 'managed-browser-driver',
supportedTargets: Object.freeze([
@@ -54,7 +54,7 @@ export const computerCapabilityCatalog: readonly ComputerCapabilityCatalogEntry[
})
]),
riskSummary:
'可读取网页内容并代表用户操作网站;当前执行不会复用命名配置,仍必须保持临时隔离和审批策略。',
'总开关关闭时不会向直连模型提供浏览器工具;开启后可在 Execute 模式直接读取网页并操作网站,不再逐次询问。',
requiredDiagnostics: Object.freeze([
'browser-executable',
'managed-profile-root'