Native Windows Gateway: browser control blocked by listener-owner verification
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- desktop-dev, security
Research direction
The failing check is the non-SSH browser authorization callback, which reportedly calls ResolveManagedDistroName and gets null for native-package Gateways; the issue cites related reports #1333 and #1691 for context. Start by reading the listener-owner verification path and the code that produces the 'could not be verified' message, then reproduce with a native Gateway setup. Done means native Gateways pass ownership verification without disabling the check, with existing settings preserved.
Written by the indexing model from the issue text.
Description
Windows Companion 2026.9.8-1; Gateway MSIX 2026.10.900.0; CLI 2026.10.9. Native isolated-session-v1 setup, without SSH or a managed WSL Gateway.
Agent chat works and browser.proxy is approved. However, requesting tabs with the user browser profile fails: “Browser control authentication was blocked because the local listener owner could not be verified.”
Restarting the Gateway restored basic connectivity. Changing the security preset from Locked Down to Recommended did not resolve the browser error.
Source review suggests that the non-SSH browser authorization callback requires ResolveManagedDistroName, while that method returns null for native-package Gateways. Could this reject a valid native Gateway? This is our analysis, not a maintainer-confirmed diagnosis.
Please confirm a supported fix or compatible version combination that preserves existing conversations and settings without disabling ownership verification. Related reports: #1333 and #1691.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 336
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 163
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openclaw/openclaw-windows-node
-
clawsweeper:fix-shape-clear clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr clawsweeper:not-repro-on-main impact:ux-release-blocker issue-rating: 🦪 silver shellfish P0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openclaw/openclaw-windows-node#1843 · 3 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-product-decision clawsweeper:needs-security-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security impact:ux-friction issue-rating: 🦞 diamond lobster P2 stale
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
openclaw/openclaw-windows-node#1763 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openclaw/openclaw-windows-node#1762 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-release-blocker issue-rating: 🦞 diamond lobster no-stale P0
Difficulty 3/5 1-2 days Newbie friendliness 20/100
openclaw/openclaw-windows-node#1983 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
bug clawsweeper:needs-live-repro clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr impact:auth-provider impact:session-state issue-rating: 🐚 platinum hermit local-models P2
Difficulty 4/5 3-5 days Newbie friendliness 18/100
openclaw/openclaw-windows-node#1976 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
All issues in openclaw/openclaw-windows-node
Similar issues
-
bug untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CarlosAdrianM/Nesto#610 ·
-
area/resource-registry status/triage
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
Altinn/altinn-auth#4821 ·
Maintainers usually reply within 1 day
-
a11y community:contribution
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/fluentui-blazor#5590 · 1 comment ·
Maintainers usually reply within 1 day
-
bug mcp small
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day