Fix profile JSON output and guidance

Author: iFurySt

cmd/open-browser-use/main.go

@@ -1446,16 +1446,6 @@ func renderProfilesList(writer io.Writer, profiles []installedChromeProfile, con
 			return err
 		}
 		fmt.Fprintln(writer, string(payload))
-		if showConnected {
-			// Surface any connected host whose instanceId didn't resolve to a known
-			// installed profile (rare; would happen if the install registered
-			// extension state under an unknown directory layout).
-			for _, info := range connected {
-				if info.Directory == "" && info.InstanceID != "" {
-					fmt.Fprintf(writer, "// unresolved connected host: socket=%s instance=%s\n", info.SocketPath, info.InstanceID)
-				}
-			}
-		}
 		return nil
 	}
 	if len(profiles) == 0 {

cmd/open-browser-use/main_test.go

@@ -630,6 +630,35 @@ func TestProfilesCommandJSONOutput(t *testing.T) {
 	}
 }
 
+func TestProfilesJSONOutputRemainsValidWithUnresolvedHost(t *testing.T) {
+	profiles := []installedChromeProfile{{
+		Directory:   "Default",
+		DisplayName: "Eva",
+		ExtensionID: defaultChromeExtensionID,
+		Version:     "0.1.10",
+		Source:      "/tmp/manifest.json",
+	}}
+	connected := []connectedProfileInfo{{
+		SocketPath: "/tmp/open-browser-use/unresolved.sock",
+		InstanceID: "11111111-aaaa-bbbb-cccc-1234567890ab",
+	}}
+
+	var output bytes.Buffer
+	if err := renderProfilesList(&output, profiles, connected, true, true); err != nil {
+		t.Fatal(err)
+	}
+	var got []map[string]any
+	if err := json.Unmarshal(output.Bytes(), &got); err != nil {
+		t.Fatalf("expected strict JSON output, got %q: %v", output.String(), err)
+	}
+	if len(got) != 1 {
+		t.Fatalf("expected one installed profile row, got %+v", got)
+	}
+	if _, ok := got[0]["connected"]; ok {
+		t.Fatalf("unresolved host should not mark installed profile connected: %+v", got[0])
+	}
+}
+
 func TestProfilesCommandHumanOutput(t *testing.T) {
 	if runtime.GOOS == "windows" {
 		t.Skip("Chrome profile detection is not implemented on windows")

docs/histories/2026-05/20260514-1805-profile-guidance-json.md

@@ -0,0 +1,21 @@
+## [2026-05-14 18:05] | Task: 收口 profile 指引与 JSON 输出
+
+用户诉求：检查 profile PR 合并后的发现，并一起处理需要修的问题。目标是多
+profile 且都装了插件时，任务开始前如果用户没指定 profile 就先询问，后续
+整轮固定使用所选 profile；代码层面只需要支持切换或连接到不同 profile。
+
+主要改动：
+
+- 修正 `obu profiles --connected --json`：JSON 模式不再追加 `// unresolved
+  connected host` footer，保证输出始终是可被脚本和 agent 解析的严格 JSON。
+- 补充回归测试，覆盖存在 unresolved connected host 时 JSON 输出仍可
+  `json.Unmarshal`。
+- 简化 `skills/open-browser-use/SKILL.md` 的多 profile 指引：多个已安装
+  profile 时先问用户选哪个；选定后整个任务持续传 `--profile`；只有所选
+  profile 未连接时才要求用户打开对应 Chrome，不自动切到其他 profile。
+
+影响文件：
+
+- `cmd/open-browser-use/main.go`
+- `cmd/open-browser-use/main_test.go`
+- `skills/open-browser-use/SKILL.md`

skills/open-browser-use/SKILL.md

@@ -52,18 +52,18 @@ picking whatever Chrome window happens to be active.
    (whether that profile's host is currently reachable). JSON output is
    available via `--json`.
 
-2. If exactly one profile is installed and its `CONNECTED` column is `yes`,
-   proceed without asking.
-
-3. If a profile is installed but `CONNECTED` is `-`, the user's Chrome is not
-   open on that profile. Ask the user to open Chrome on that profile (naming it
-   by display name so it is unambiguous) before retrying — do not run browser
-   commands yet, the connection will just fail.
-
-4. If more than one profile is installed and connected, ask the user which to
-   use unless the user already specified one in the original task ("use my work
-   profile", "do this on cookiy.com"). When asking, list both directory name
-   and display name so the user can recognize them.
+2. If exactly one profile is installed and connected, proceed without asking.
+   If it is installed but not connected, ask the user to open Chrome on that
+   profile before running browser commands.
+
+3. If multiple profiles are installed and the user did not already specify
+   which one to use, ask before the first browser command. List both directory
+   name and display name so the user can recognize them, and include whether
+   each profile is connected.
+
+4. If the chosen profile is not connected, ask the user to open Chrome on that
+   profile before retrying. Do not silently fall back to a different connected
+   profile.
 
 5. After the user has chosen, pass `--profile <selector>` to every CLI / MCP
    command for the rest of the task. The selector accepts either the directory