[FEATURE] Show the requesting session/task name in the Claude in Chrome connection prompt
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
When Claude Desktop or Claude Code requests a browser connection, the Claude in Chrome extension shows a pairing prompt that only says "Claude Desktop wants to connect" (i18n key NkHG2fB0cW; {clientLabel} is hardcoded to either "Claude Desktop" or "Claude Code" in PairingPrompt).
When multiple sessions are running at the same time (common for business users who combine scheduled routines with interactive sessions), there is no way to tell which conversation/task triggered the pairing request. The user risks approving the connection in the wrong Chrome window/profile, which can disrupt another session's in-progress browser work.
Alternatives considered
- Naming each browser at pairing time: helps identify browsers, but not which task is requesting the connection.
- Announcing the purpose in chat right before calling
switch_browser: works, but only if the user is watching that specific conversation at that moment. - Editing the extension's i18n strings locally: not viable (content verification), and the session name is not present in the payload anyway.
Environment
- Claude Desktop on Windows 11, Claude in Chrome extension v1.0.85
- Japanese UI (the prompt shows as 「Claude Desktop が接続をリクエストしています」)
Proposed Solution
Include the requesting session's title (or a short task label) in the pairing request payload sent to the Claude in Chrome extension, and render it in the pairing prompt, e.g.:
"Claude Desktop — session 'Greeze year-end filing' — wants to connect"
A truncated session title (with the same privacy treatment as the session list in the Desktop app) would be enough to disambiguate which task is asking for the connection. Ideally the same label would also appear in the browser-naming step, so users approving a connection always know which conversation they are approving it for.
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_