{"timestamp":"2026-09-04T05:54:59.509285Z","level":"INFO","fields":{"message":"daemon lock acquired"}}
{"timestamp":"2026-09-04T05:54:59.909589Z","level":"INFO","fields":{"message":"daemon ready","pid":21848,"ws_port":52800}}
{"timestamp":"2026-09-04T05:54:59.909803Z","level":"INFO","fields":{"message":"ipc named-pipe server listening","pipe":"\\\\.\\pipe\\bsk-daemon-<hash>"}}
{"timestamp":"2026-09-04T05:55:03.478828Z","level":"INFO","fields":{"message":"browser connected","id":"<browser-id>","name":"chrome","generation":1}}
{"timestamp":"2026-09-04T05:55:39.482121Z","level":"INFO","fields":{"message":"daemon lock acquired"}}
{"timestamp":"2026-09-04T05:55:39.841814Z","level":"INFO","fields":{"message":"daemon ready","pid":159092,"ws_port":52800}}
{"timestamp":"2026-09-04T05:55:39.935152Z","level":"INFO","fields":{"message":"browser connected","id":"<browser-id>","name":"chrome","generation":1}}
{"timestamp":"2026-09-04T05:56:01.452183Z","level":"INFO","fields":{"message":"daemon lock acquired"}}
{"timestamp":"2026-09-04T05:56:01.947870Z","level":"INFO","fields":{"message":"daemon ready","pid":141308,"ws_port":52800}}
环境信息
~/.local/bin/bsk.exe~/.bsk问题概述
从 bsk 0.1.11 升级至 0.2.0 后,daemon 可正常启动且浏览器扩展可连接,但会话无法使用。
bsk session start能返回会话 ID,但任何后续命令(如bsk navigate)均立即失败,提示session not registered or already stopped。复现步骤
bsk daemon start(或等待自动启动)。bsk status→ daemon 显示0.2.0,browsers connected: 1。bsk session start→ 返回 4 位字母会话 ID(如dfhj)。bsk navigate <url> --session <id>→ 立即失败。预期行为
会话应保持注册状态,
bsk navigate应在 Agent Window 中打开目标 URL。实际行为
bsk session list确认输出为(no active sessions)。补充诊断
bsk doctor报告:daemon running: FAIL — pid is alive but IPC is unreachable: connect IPC named pipe \\.\pipe\bsk-daemon-<hash>bsk daemon restart在停止阶段失败,退出码为 2。bsk daemon start可拉起新 daemon 进程,bsk status随后显示正常,但会话注册失败问题依旧。daemon lock acquired/daemon ready/browser connected循环,表明 daemon 可能在持续崩溃-重启。日志
daemon 日志节选(反复重启)
临时解决方案
暂未发现可用方案。回退至 0.1.11 可恢复功能,但 0.1.11 自身存在更新暂存文件(
bsk.exe.update-*)无法应用的问题。影响范围
此问题阻断 Windows 平台升级至 0.2.0 后的所有浏览器自动化工作流。