Browser/X primary-source path — approval and verification

過去レポートのView/ソース規律バックフィルで生成したView。

Generated: 2026-05-10T14:50:00+09:00

健人くん explicitly approved the browser/operator scope upgrade in Telegram. After approval, I verified the browser path with local OpenClaw browser automation.

Approval result

The CLI device scope upgrade was approved via OpenClaw's local device-pairing implementation after the normal openclaw devices approve <id> path kept superseding the request id during reconnect.

Approved scopes now include:

operator.admin
operator.approvals
operator.pairing
operator.read
operator.talk.secrets
operator.write

Post-approval openclaw devices list --json showed:

pending: []
paired CLI device with the requested operator scopes

Browser control verification

openclaw browser doctor after approval:

OK gateway: browser control endpoint reachable
OK plugin: enabled
OK profile: openclaw (cdp)
FAIL browser: not running; run `openclaw browser start`
OK profiles: 2 configured

Then openclaw browser --browser-profile openclaw start succeeded.

Deep doctor after start:

OK gateway: browser control endpoint reachable
OK plugin: enabled
OK profile: openclaw (cdp)
OK browser: running
OK profiles: 2 configured
OK tabs: 3 visible, use target t1
OK live-snapshot: 25 nodes/lines

Example page proof:

Opened https://example.com/`


Snapshot returned the expected Example Domain accessibility tree.


X public page verification
Opened:
https://x.com/addyosmani
Snapshot confirmed page access and readable profile content, including:

title: Addy Osmani（@addyosmani）さん / X
profile name: Addy Osmani
handle: @addyosmani
profile text referencing Google Cloud AI / Gemini / agents
follower/following counts

So public X profile inspection through the managed OpenClaw browser profile works.
Remaining limitation
The user existing-session profile is not currently usable:
Chrome MCP existing-session attach for profile "user" timed out after 600ms.
Could not connect to Chrome. Check if Chrome is running.
Could not find DevToolsActivePort for chrome at /Users/aiharataketo/Library/Application Support/Google/Chrome/DevToolsActivePort
Meaning: signed-in personal Chrome/X session is still not available. Public X pages can be checked through the managed openclaw profile; login-only content still requires a separate Chrome MCP/user-profile setup step and should not be implied as checked.
Operating rule
For future research depending on X/browser-only primary sources:

Public X/browser sources: use openclaw browser profile and cite what was actually observed.
Login-only/private X sources: say the signed-in user browser is unavailable unless/until user profile is fixed.
Never imply browser/X verification if only web search or secondary pages were used.