Skip to content

Commit 6473d5e

Browse files
feat(desktop): in-process browser MCP servers — no sidecars, no npx (anomalyco#1676)
* feat(desktop): in-process browser MCP servers using chrome-devtools-mcp as library Import chrome-devtools-mcp tools, McpContext, and McpResponse as library modules (never import main.js — it has CLI side effects). Two MCP servers run inside the Electron main process: openwork-browser — controls the embedded WebContentsView via Electron's own CDP endpoint. Auto-opens the browser panel when a tool is called. chrome — connects to the user's external Chrome (port 9222/9229) for controlling their real browser with cookies, extensions, etc. Both are exposed as HTTP MCP endpoints (StreamableHTTPServerTransport) and auto-injected into opencode.json as remote MCP servers. Legacy local chrome-devtools and control-chrome entries are cleaned up. No sidecars, no npx, no absolute paths. The chrome-devtools-mcp npm package ships as a dependency and its tools run in-process. Architecture: Electron main process ├── browser-mcp.mjs (imports chrome-devtools-mcp pieces) │ ├── McpServer + tools from chrome-devtools-mcp │ ├── puppeteer.connect(browserURL) for CDP │ └── StreamableHTTPServerTransport on localhost ├── WebContentsView (built-in browser, demand-driven) └── opencode.json: { mcp: { openwork-browser: {type:remote}, chrome: {type:remote} } } Verified: - Both servers start and respond to /health - opencode.jsonc gets correct remote MCP entries - App detects config change and offers reload - All 17 existing tests pass * fix(desktop): target WebContentsView only for built-in browser MCP, not main renderer The built-in browser MCP server was controlling the main OpenWork renderer (localhost:5173) instead of the embedded WebContentsView because puppeteer.connect() picked whichever CDP target came first. Fixes: - Add BUILTIN_TARGET_FILTER that excludes file://, localhost, 127.0.0.1 and about:blank — only real websites in the WebContentsView match - Separate connectBuiltinBrowser vs connectExternalBrowser functions - Make onBuiltinToolCall async — it now creates the WebContentsView and waits for the default URL to load BEFORE the tool handler connects via puppeteer, ensuring the target exists - Force reconnect on each built-in tool call so puppeteer always sees the latest WebContentsView target (not a stale connection from before the view was created) * fix(desktop): open browser panel on every built-in tool call, add show/hide tools - Use browserViewVisible flag (not DOM children check) to reliably detect whether the panel needs opening - Every openwork-browser tool call ensures the panel is visible before puppeteer connects — the agent can't interact with an invisible panel - Add show_browser tool: explicitly open the panel (also auto-called) - Add hide_browser tool: close the panel when the task is done - onHideBrowser callback in main.mjs sends panel-closed event to renderer - External chrome MCP is untouched — it never touches the panel * feat(agent): update openwork.md with browser tool instructions The default agent now knows about both browser MCP servers and when to use each one: - openwork-browser (built-in): default for general browsing, panel auto-opens, call hide_browser when done - chrome (external): use when the user needs real cookies/extensions Updated in both the server workspace-init.ts (Electron path) and the Tauri files.rs. Removed the old 'ask user to add Control Chrome' instruction since browser tools are now built-in and always available. * fix(desktop): sync browser panel React UI with main process open/close events When the agent calls a built-in browser tool, the main process opens the WebContentsView but the React BrowserPanel component wasn't being rendered — so no toolbar (URL bar, back/forward, close button). Fix: the main process sends panel-opened/panel-closed IPC events, the preload exposes onPanelOpened/onPanelClosed listeners, and session-page subscribes to them to set browserPanelOpen state. Now both paths (user clicks Browser button, or agent calls a tool) produce the same UI with the full toolbar. * fix(desktop): fix MCP HTTP server session handling — one server per session The previous implementation called mcpServer.connect(transport) for every new session on a single McpServer instance. McpServer only supports one transport at a time, so subsequent sessions would hang. Fix: startMcpHttpServer now takes a factory function instead of a server instance. Each new MCP session (no mcp-session-id header) creates a fresh server+transport pair. Existing sessions reuse their transport via the session ID header. This matches how StreamableHTTPServerTransport is designed to work and should fix OpenCode failing to connect to the remote MCP servers. * chore(desktop): remove legacy Control Chrome connector UI and sidecar remnants Remove the old user-facing Control Chrome connector flow now that browser automation is built into OpenWork: - remove Chrome quick-connect entry and npx command constants - remove ControlChromeSetupModal and settings UI buttons - remove chrome-devtools local command resolution helpers from mcp.ts/store.ts - remove obsolete chrome-devtools-mcp shim script and sidecar prep metadata - remove Control Chrome / quick-connect Chrome i18n keys - keep only an internal migration cleanup that deletes legacy control-chrome config entries from existing workspaces Verified no user-facing Control Chrome references remain in app/server/electron/scripts. * fix(desktop): preserve built-in browser MCP context across snapshot and input tools The built-in browser MCP was reconnecting Puppeteer on every tool call. chrome-devtools-mcp stores the latest accessibility snapshot on its McpContext, so reconnecting after take_snapshot created a fresh context and follow-up fill/click calls failed with 'No snapshot found'. Now the built-in browser connection is reused while connected. The WebContentsView is still opened before the first tool call, so the initial connection targets the panel, but subsequent tools preserve snapshot state and UID mappings. * fix(desktop): guide external Chrome connection setup
1 parent 03bb660 commit 6473d5e

27 files changed

Lines changed: 860 additions & 744 deletions

‎apps/app/src/app/constants.ts‎

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,6 @@ export type McpDirectoryInfo = {
2525
oauth: boolean;
2626
};
2727

28-
export const CHROME_DEVTOOLS_MCP_ID = "chrome-devtools";
29-
export const CHROME_DEVTOOLS_MCP_COMMAND = ["npx", "-y", "chrome-devtools-mcp@latest"] as const;
30-
3128
export const MCP_QUICK_CONNECT: McpDirectoryInfo[] = [
3229
{
3330
get name() { return t("mcp.quick_connect_notion_title"); },
@@ -64,12 +61,4 @@ export const MCP_QUICK_CONNECT: McpDirectoryInfo[] = [
6461
type: "remote",
6562
oauth: false,
6663
},
67-
{
68-
id: CHROME_DEVTOOLS_MCP_ID,
69-
get name() { return t("mcp.quick_connect_chrome_title"); },
70-
get description() { return t("mcp.quick_connect_chrome_desc"); },
71-
type: "local",
72-
command: [...CHROME_DEVTOOLS_MCP_COMMAND],
73-
oauth: false,
74-
},
7564
];

‎apps/app/src/app/lib/desktop.ts‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,8 @@ declare global {
7777
getState?: () => Promise<{ url: string; title: string; canGoBack: boolean; canGoForward: boolean; isLoading: boolean } | null>;
7878
destroy?: () => Promise<void>;
7979
onStateChange?: (callback: (state: { url: string; title: string; canGoBack: boolean; canGoForward: boolean; isLoading: boolean }) => void) => () => void;
80+
onPanelOpened?: (callback: () => void) => () => void;
81+
onPanelClosed?: (callback: () => void) => () => void;
8082
};
8183
meta?: {
8284
initialDeepLinks?: string[];

‎apps/app/src/app/mcp.ts‎

Lines changed: 0 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,9 @@
11
import { applyEdits, modify, parse, printParseErrorCode } from "jsonc-parser";
22
import type { McpServerConfig, McpServerEntry } from "./types";
33
import { readOpencodeConfig, writeOpencodeConfig } from "./lib/desktop";
4-
import { CHROME_DEVTOOLS_MCP_COMMAND, CHROME_DEVTOOLS_MCP_ID } from "./constants";
5-
import { isElectronRuntime } from "./utils";
64

75
type McpConfigValue = Record<string, unknown> | null | undefined;
86

9-
export const CHROME_DEVTOOLS_AUTO_CONNECT_ARG = "--autoConnect";
10-
11-
/**
12-
* Cached result of resolving the bundled chrome-devtools-mcp binary path
13-
* from the Electron main process. `undefined` = not yet resolved.
14-
*/
15-
let _resolvedBundledCommand: string[] | null | undefined;
16-
17-
/**
18-
* Resolve the chrome-devtools-mcp command for the current runtime.
19-
*
20-
* In Electron, the package is bundled as a dependency of `@openwork/desktop`,
21-
* so we ask the main process for the absolute path to the bin and use
22-
* `["node", "<path>"]` — no npm/npx required.
23-
*
24-
* Falls back to the npx-based command for web/remote contexts.
25-
*/
26-
export async function resolveChromeDevtoolsMcpCommand(): Promise<string[]> {
27-
if (isElectronRuntime() && _resolvedBundledCommand === undefined) {
28-
try {
29-
const resolved = await (window as Window).__OPENWORK_ELECTRON__!.invokeDesktop(
30-
"resolveChromeDevtoolsMcpBin",
31-
);
32-
_resolvedBundledCommand = Array.isArray(resolved) && resolved.length > 0
33-
? (resolved as string[])
34-
: null;
35-
} catch {
36-
_resolvedBundledCommand = null;
37-
}
38-
}
39-
return _resolvedBundledCommand ?? [...CHROME_DEVTOOLS_MCP_COMMAND];
40-
}
41-
427
type McpIdentity = {
438
id?: string;
449
name: string;
@@ -52,27 +17,6 @@ export function getMcpIdentityKey(entry: McpIdentity): string {
5217
return entry.id ?? normalizeMcpSlug(entry.name);
5318
}
5419

55-
export function isChromeDevtoolsMcp(entry: McpIdentity | string | null | undefined): boolean {
56-
if (!entry) return false;
57-
const key = typeof entry === "string" ? entry : getMcpIdentityKey(entry);
58-
return key === CHROME_DEVTOOLS_MCP_ID || normalizeMcpSlug(typeof entry === "string" ? entry : entry.name) === "control-chrome";
59-
}
60-
61-
export function usesChromeDevtoolsAutoConnect(command?: string[]): boolean {
62-
return Array.isArray(command) && command.includes(CHROME_DEVTOOLS_AUTO_CONNECT_ARG);
63-
}
64-
65-
export function buildChromeDevtoolsCommand(
66-
command: string[] | undefined,
67-
useExistingProfile: boolean,
68-
resolvedBase?: string[],
69-
): string[] {
70-
const base = Array.isArray(command) && command.length
71-
? command.filter((part) => part !== CHROME_DEVTOOLS_AUTO_CONNECT_ARG)
72-
: resolvedBase ?? [...CHROME_DEVTOOLS_MCP_COMMAND];
73-
return useExistingProfile ? [...base, CHROME_DEVTOOLS_AUTO_CONNECT_ARG] : base;
74-
}
75-
7620
export function validateMcpServerName(name: string): string {
7721
const trimmed = name.trim();
7822
if (!trimmed) {

‎apps/app/src/i18n/locales/ca.ts‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -584,23 +584,6 @@ export default {
584584
"mcp.connected_badge": "Connectat",
585585
"mcp.connection_failed": "Problema de connexió: torna-ho a provar",
586586
"mcp.connection_type": "Connexió",
587-
"mcp.control_chrome_browser_hint": "A Chrome 144 o superior, fes això primer:",
588-
"mcp.control_chrome_browser_step_one": "Obre chrome://inspect/#remote-debugging.",
589-
"mcp.control_chrome_browser_step_two": "Activa la depuració remota.",
590-
"mcp.control_chrome_browser_step_three": "Permet connexions de depuració entrants quan Chrome ho demani.",
591-
"mcp.control_chrome_browser_title": "1. Activa l'accés a Chrome",
592-
"mcp.control_chrome_connect": "Afegeix Control Chrome",
593-
"mcp.control_chrome_docs": "Guia oficial MCP",
594-
"mcp.control_chrome_edit": "Edita la configuració",
595-
"mcp.control_chrome_profile_hint": "Control Chrome normalment obre un perfil Chrome independent. Activeu-ho si voleu que OpenWork reutilitzi la finestra Chrome que ja teniu oberta.",
596-
"mcp.control_chrome_profile_title": "2. Tria quin Chrome vols fer servir",
597-
"mcp.control_chrome_save": "Desa la configuració",
598-
"mcp.control_chrome_setup_subtitle": "Activa l'accés a Chrome i tria si OpenWork ha de fer servir un perfil net propi o enganxar-se al Chrome que ja tens obert.",
599-
"mcp.control_chrome_setup_title": "Configura Control Chrome",
600-
"mcp.control_chrome_toggle_hint": "Quan això està activat, OpenWork afegeix --autoConnect de manera que el MCP s'adjunta a una instància Chrome que ja heu iniciat.",
601-
"mcp.control_chrome_toggle_label": "Utilitza el meu perfil Chrome existent",
602-
"mcp.control_chrome_toggle_off": "OpenWork llançarà un perfil Chrome independent només per a l'automatització.",
603-
"mcp.control_chrome_toggle_on": "OpenWork reutilitzarà les vostres pestanyes, galetes i inicis de sessió actuals.",
604587
"mcp.custom_app_cta_hint": "Connecta el teu servidor MCP, una eina interna o una app allotjada.",
605588
"mcp.desktop_required": "Les aplicacions requereixen el app d'escriptori.",
606589
"mcp.docs_link": "Més informació",
@@ -633,8 +616,6 @@ export default {
633616
"mcp.opening_label": "S'està obrint...",
634617
"mcp.pick_workspace_error": "Tria primer una carpeta de workspace.",
635618
"mcp.pick_workspace_first": "Tria primer una carpeta de workspace.",
636-
"mcp.quick_connect_chrome_desc": "Controla pestanyes de Chrome amb automatització del navegador.",
637-
"mcp.quick_connect_chrome_title": "Control Chrome",
638619
"mcp.quick_connect_context7_desc": "Cerca documentació del producte amb més context.",
639620
"mcp.quick_connect_context7_title": "Context7",
640621
"mcp.quick_connect_linear_desc": "Planifica sprints i lliura tickets més de pressa.",

‎apps/app/src/i18n/locales/en.ts‎

Lines changed: 20 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,26 @@ export default {
7777
"common.something_went_wrong": "Something went wrong",
7878
"common.submit": "Submit",
7979
"common.unknown": "Unknown",
80+
"chrome_setup.badge": "Chrome Connection",
81+
"chrome_setup.close": "Close",
82+
"chrome_setup.connected_message": "Chrome is connected. OpenWork can now control your browser, including your tabs, cookies, and sign-ins.",
83+
"chrome_setup.docs_link": "Chrome remote debugging docs",
84+
"chrome_setup.done": "Done",
85+
"chrome_setup.info_what_this_enables": "When connected, OpenWork can navigate tabs, fill forms, and read pages in your real Chrome — including sites where you're signed in. You can disconnect at any time by disabling remote debugging in Chrome.",
86+
"chrome_setup.status_checking": "Checking connection...",
87+
"chrome_setup.status_connected": "Chrome connected",
88+
"chrome_setup.status_unavailable": "Chrome not reachable — follow the steps below",
89+
"chrome_setup.status_unknown": "Not checked yet",
90+
"chrome_setup.step_one_allow": "Allow incoming debugging connections when Chrome asks.",
91+
"chrome_setup.step_one_enable": "Enable remote debugging.",
92+
"chrome_setup.step_one_hint": "Chrome 144+ lets you enable this without restarting. Your existing tabs, cookies, and sign-ins stay intact.",
93+
"chrome_setup.step_one_open_inspect": "In Chrome, go to",
94+
"chrome_setup.step_one_title": "Turn on Chrome remote debugging",
95+
"chrome_setup.step_two_hint": "After enabling remote debugging, click the button below to verify OpenWork can reach Chrome.",
96+
"chrome_setup.step_two_title": "Test the connection",
97+
"chrome_setup.subtitle": "Let OpenWork control your real Chrome browser — your tabs, cookies, and sign-ins — so it can work with sites where you're already logged in.",
98+
"chrome_setup.test_connection": "Test connection",
99+
"chrome_setup.title": "Connect your Chrome",
80100
"composer.agent_label": "Agent",
81101
"composer.any_file_type_supported": "Any file type is supported.",
82102
"composer.attach_files": "Attach files",
@@ -595,23 +615,6 @@ export default {
595615
"mcp.connected_badge": "Connected",
596616
"mcp.connection_failed": "Connection issue — try again",
597617
"mcp.connection_type": "Connection",
598-
"mcp.control_chrome_browser_hint": "In Chrome 144 or newer, do this first:",
599-
"mcp.control_chrome_browser_step_one": "Open chrome://inspect/#remote-debugging.",
600-
"mcp.control_chrome_browser_step_two": "Enable remote debugging.",
601-
"mcp.control_chrome_browser_step_three": "Allow incoming debugging connections when Chrome asks.",
602-
"mcp.control_chrome_browser_title": "1. Turn on Chrome access",
603-
"mcp.control_chrome_connect": "Add Control Chrome",
604-
"mcp.control_chrome_docs": "Official MCP guide",
605-
"mcp.control_chrome_edit": "Edit settings",
606-
"mcp.control_chrome_profile_hint": "Control Chrome normally opens a separate Chrome profile. Turn this on if you want OpenWork to reuse the Chrome window you already have open.",
607-
"mcp.control_chrome_profile_title": "2. Choose which Chrome to use",
608-
"mcp.control_chrome_save": "Save settings",
609-
"mcp.control_chrome_setup_subtitle": "Turn on Chrome access, then choose whether OpenWork should use its own clean profile or attach to the Chrome you already use.",
610-
"mcp.control_chrome_setup_title": "Set up Control Chrome",
611-
"mcp.control_chrome_toggle_hint": "When this is on, OpenWork adds --autoConnect so the MCP attaches to a Chrome instance you already started.",
612-
"mcp.control_chrome_toggle_label": "Use my existing Chrome profile",
613-
"mcp.control_chrome_toggle_off": "OpenWork will launch a separate Chrome profile just for automation.",
614-
"mcp.control_chrome_toggle_on": "OpenWork will reuse your current tabs, cookies, and sign-ins.",
615618
"mcp.custom_app_cta_hint": "Connect your own MCP server, internal tool, or hosted app.",
616619
"mcp.desktop_required": "Apps require the desktop app.",
617620
"mcp.docs_link": "Learn more",
@@ -644,8 +647,6 @@ export default {
644647
"mcp.opening_label": "Opening...",
645648
"mcp.pick_workspace_error": "Choose a workspace folder first.",
646649
"mcp.pick_workspace_first": "Choose a workspace folder first.",
647-
"mcp.quick_connect_chrome_desc": "Drive Chrome tabs with browser automation.",
648-
"mcp.quick_connect_chrome_title": "Control Chrome",
649650
"mcp.quick_connect_context7_desc": "Search product docs with richer context.",
650651
"mcp.quick_connect_context7_title": "Context7",
651652
"mcp.quick_connect_linear_desc": "Plan sprints and ship tickets faster.",

‎apps/app/src/i18n/locales/es.ts‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -584,23 +584,6 @@ export default {
584584
"mcp.connected_badge": "Conectado",
585585
"mcp.connection_failed": "Problema de conexión: inténtalo de nuevo",
586586
"mcp.connection_type": "Conexión",
587-
"mcp.control_chrome_browser_hint": "En Chrome 144 o posterior, haz esto primero:",
588-
"mcp.control_chrome_browser_step_one": "Abre `chrome://inspect/#remote-debugging`.",
589-
"mcp.control_chrome_browser_step_two": "Activa la depuración remota.",
590-
"mcp.control_chrome_browser_step_three": "Permite las conexiones de depuración entrantes cuando Chrome te lo pida.",
591-
"mcp.control_chrome_browser_title": "1. Activa el acceso a Chrome",
592-
"mcp.control_chrome_connect": "Añadir Control Chrome",
593-
"mcp.control_chrome_docs": "Guía oficial MCP",
594-
"mcp.control_chrome_edit": "Editar configuración",
595-
"mcp.control_chrome_profile_hint": "Control Chrome suele abrir un perfil de Chrome aparte. Activa esta opción si quieres que OpenWork reutilice la ventana de Chrome que ya tienes abierta.",
596-
"mcp.control_chrome_profile_title": "2. Elige qué Chrome usar",
597-
"mcp.control_chrome_save": "Guardar configuración",
598-
"mcp.control_chrome_setup_subtitle": "Activa el acceso a Chrome y luego elige si OpenWork debe usar un perfil limpio propio o conectarse al Chrome que ya usas.",
599-
"mcp.control_chrome_setup_title": "Configurar Control Chrome",
600-
"mcp.control_chrome_toggle_hint": "Cuando esto está activado, OpenWork añade --autoConnect para que MCP se conecte a una instancia de Chrome que ya has abierto.",
601-
"mcp.control_chrome_toggle_label": "Usar mi perfil Chrome existente",
602-
"mcp.control_chrome_toggle_off": "OpenWork abrirá un perfil de Chrome aparte solo para la automatización.",
603-
"mcp.control_chrome_toggle_on": "OpenWork reutilizará tus pestañas, cookies e inicios de sesión actuales.",
604587
"mcp.custom_app_cta_hint": "Conecta tu propio servidor MCP, herramienta interna o app alojada.",
605588
"mcp.desktop_required": "Las apps requieren la app de escritorio.",
606589
"mcp.docs_link": "Más información",
@@ -633,8 +616,6 @@ export default {
633616
"mcp.opening_label": "Abriendo...",
634617
"mcp.pick_workspace_error": "Elige primero una carpeta del espacio de trabajo.",
635618
"mcp.pick_workspace_first": "Elige primero una carpeta del espacio de trabajo.",
636-
"mcp.quick_connect_chrome_desc": "Controla pestañas de Chrome con automatización del navegador.",
637-
"mcp.quick_connect_chrome_title": "Control Chrome",
638619
"mcp.quick_connect_context7_desc": "Busca documentación del producto con más contexto.",
639620
"mcp.quick_connect_context7_title": "Context7",
640621
"mcp.quick_connect_linear_desc": "Planifica sprints y lanza tickets más rápido.",

‎apps/app/src/i18n/locales/fr.ts‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -584,23 +584,6 @@ export default {
584584
"mcp.connected_badge": "Connecté",
585585
"mcp.connection_failed": "Problème de connexion — réessayez",
586586
"mcp.connection_type": "Connexion",
587-
"mcp.control_chrome_browser_hint": "Dans Chrome 144 ou version ultérieure, faites d'abord ceci :",
588-
"mcp.control_chrome_browser_step_one": "Ouvrez chrome://inspect/#remote-debugging.",
589-
"mcp.control_chrome_browser_step_two": "Activez le débogage à distance.",
590-
"mcp.control_chrome_browser_step_three": "Autorisez les connexions de débogage entrantes lorsque Chrome le demande.",
591-
"mcp.control_chrome_browser_title": "1. Activer l'accès à Chrome",
592-
"mcp.control_chrome_connect": "Ajouter Control Chrome",
593-
"mcp.control_chrome_docs": "Guide MCP officiel",
594-
"mcp.control_chrome_edit": "Modifier les paramètres",
595-
"mcp.control_chrome_profile_hint": "Control Chrome ouvre normalement un profil Chrome séparé. Activez ceci si vous voulez qu'OpenWork réutilise la fenêtre Chrome déjà ouverte.",
596-
"mcp.control_chrome_profile_title": "2. Choisir quel Chrome utiliser",
597-
"mcp.control_chrome_save": "Enregistrer les paramètres",
598-
"mcp.control_chrome_setup_subtitle": "Activez l'accès à Chrome, puis choisissez si OpenWork doit utiliser son propre profil propre ou se rattacher au Chrome que vous utilisez déjà.",
599-
"mcp.control_chrome_setup_title": "Configurer Control Chrome",
600-
"mcp.control_chrome_toggle_hint": "Lorsque cette option est activée, OpenWork ajoute --autoConnect pour que le MCP se rattache à une instance Chrome que vous avez déjà démarrée.",
601-
"mcp.control_chrome_toggle_label": "Utiliser mon profil Chrome existant",
602-
"mcp.control_chrome_toggle_off": "OpenWork lancera un profil Chrome séparé uniquement pour l'automatisation.",
603-
"mcp.control_chrome_toggle_on": "OpenWork réutilisera vos onglets, cookies et connexions actuels.",
604587
"mcp.custom_app_cta_hint": "Connectez votre propre serveur MCP, outil interne ou application hébergée.",
605588
"mcp.desktop_required": "Les applications nécessitent l'application desktop.",
606589
"mcp.docs_link": "En savoir plus",
@@ -633,8 +616,6 @@ export default {
633616
"mcp.opening_label": "Ouverture...",
634617
"mcp.pick_workspace_error": "Choisissez d'abord un dossier d'espace de travail.",
635618
"mcp.pick_workspace_first": "Choisissez d'abord un dossier d'espace de travail.",
636-
"mcp.quick_connect_chrome_desc": "Pilotez les onglets Chrome avec l'automatisation du navigateur.",
637-
"mcp.quick_connect_chrome_title": "Control Chrome",
638619
"mcp.quick_connect_context7_desc": "Recherchez dans la documentation produit avec un contexte plus riche.",
639620
"mcp.quick_connect_context7_title": "Context7",
640621
"mcp.quick_connect_linear_desc": "Planifiez les sprints et livrez les tickets plus vite.",

‎apps/app/src/i18n/locales/ja.ts‎

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -561,23 +561,6 @@ export default {
561561
"mcp.connected_badge": "接続済み",
562562
"mcp.connection_failed": "接続の問題 — 再試行してください",
563563
"mcp.connection_type": "接続",
564-
"mcp.control_chrome_browser_hint": "Chrome 144以降では、まず次の手順を実行してください:",
565-
"mcp.control_chrome_browser_step_one": "chrome://inspect/#remote-debuggingを開く。",
566-
"mcp.control_chrome_browser_step_two": "リモートデバッグを有効にする。",
567-
"mcp.control_chrome_browser_step_three": "Chromeが求めたらデバッグ接続を許可する。",
568-
"mcp.control_chrome_browser_title": "1. Chromeアクセスを有効にする",
569-
"mcp.control_chrome_connect": "Control Chromeを追加",
570-
"mcp.control_chrome_docs": "公式MCPガイド",
571-
"mcp.control_chrome_edit": "設定を編集",
572-
"mcp.control_chrome_profile_hint": "Control Chromeは通常、別のChromeプロファイルを開きます。すでに開いているChromeウィンドウをOpenWorkで再利用したい場合はこれをオンにしてください。",
573-
"mcp.control_chrome_profile_title": "2. 使用するChromeを選択",
574-
"mcp.control_chrome_save": "設定を保存",
575-
"mcp.control_chrome_setup_subtitle": "Chromeアクセスを有効にし、OpenWorkが独自のクリーンプロファイルを使うか、すでに使用しているChromeに接続するかを選択します。",
576-
"mcp.control_chrome_setup_title": "Control Chromeのセットアップ",
577-
"mcp.control_chrome_toggle_hint": "オンにすると、OpenWorkが--autoConnectを追加し、すでに起動しているChromeインスタンスにMCPが接続します。",
578-
"mcp.control_chrome_toggle_label": "既存のChromeプロファイルを使用",
579-
"mcp.control_chrome_toggle_off": "OpenWorkは自動化専用の別のChromeプロファイルを起動します。",
580-
"mcp.control_chrome_toggle_on": "OpenWorkは現在のタブ、Cookie、サインイン情報を再利用します。",
581564
"mcp.custom_app_cta_hint": "独自のMCPサーバー、社内ツール、またはホスト型アプリを接続します。",
582565
"mcp.desktop_required": "アプリにはデスクトップアプリが必要です。",
583566
"mcp.docs_link": "詳細を見る",
@@ -610,8 +593,6 @@ export default {
610593
"mcp.opening_label": "開いています…",
611594
"mcp.pick_workspace_error": "最初にワークスペースフォルダを選択してください。",
612595
"mcp.pick_workspace_first": "最初にワークスペースフォルダを選択してください。",
613-
"mcp.quick_connect_chrome_desc": "ブラウザ自動化でChromeタブを操作。",
614-
"mcp.quick_connect_chrome_title": "Chromeを操作",
615596
"mcp.quick_connect_context7_desc": "より豊富なコンテキストで製品ドキュメントを検索。",
616597
"mcp.quick_connect_context7_title": "Context7",
617598
"mcp.quick_connect_linear_desc": "スプリントを計画し、チケットをより速く処理。",

0 commit comments

Comments
 (0)