[liuhedev]

Every Agent Window currently labels its native tab group BrowserSkill, so concurrent tasks are indistinguishable. This change reuses bsk session start --name as the group title, while retaining its existing use in local operation history.

bsk session start --name "账户变更" --browser <browser-id>

The group's title becomes 账户变更. Names are trimmed for display; omitted or whitespace-only names retain BrowserSkill. No additional CLI flag is needed.

The daemon forwards the optional task_name field through tool.session_start; the extension retains it in the session context and uses it when reconciling its own group. The protocol schema, CLI help, and documentation are updated. Group ownership, orange color, collapsed-state preservation, and page-control rules are unchanged. Both the daemon and extension need the update; older peers retain the default title.

Validation

• Extension TypeScript compilation, targeted Biome checks, extension production build, and git diff --check: passed.
• Existing session-manager, tab-group, and session-handler suites: 69 tests passed.
• Protocol compilation, schema generation, and existing protocol suite: 174 tests passed.
• Live integration with an isolated Chrome for Testing 151.0.7922.34 profile, calling the production session-start handler and real Chrome tab-group APIs:

Input task name	Actual group title
账户变更	账户变更
日志排查	日志排查
omitted	BrowserSkill
whitespace only	BrowserSkill

All four sessions received distinct groups. A newly claimed tab joined its session's group without changing its title or expanding a collapsed group. A non-string task name was rejected.

Validation gap: the full CLI/daemon build could not complete locally because the aws-lc-sys dependency was unavailable in the local cache and dependency downloads were unreliable. The live browser check covers the extension handler through the native group APIs, rather than a complete CLI-to-daemon-to-extension round trip. The Draft PR is pending the repository's CI and maintainer review.