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
+2 -2
View File
@@ -106,9 +106,9 @@ export const builtinModelToolGroups = [
},
{
id: 'browser',
name: '浏览器操作',
name: '内置浏览器',
description:
'启用“浏览器控制”后,在 Execute 模式下操作 GoodBuddy 隔离浏览器。',
'启用“内置浏览器”后,在 Execute 模式下操作 GoodBuddy 隔离浏览器。',
tools: builtinModelTools.filter((tool) => tool.group === 'browser')
},
{