Repeated Browser runtime attachment failure a
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Feedback ID
01a044a5-a68f-7e01-a1d6-c938671d9047
Repeated Browser runtime attachment failure after multiple full restarts and new tasks. Browser plugin 26.820.60940 is installed, browser-client.mjs exists, and the in-app Browser service is running. However, the trusted browser-control tool is not exposed to the task. Direct connection reaches the service but is rejected as untrusted. Consequently, @Browser cannot list or inspect open tabs. Desktop build: 151.0.7922.170. Please escalate as a desktop runtime/tool-attachment defect—not a browser authentication or user-configuration issue.
Contributor 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.
Research direction
Start with the reported desktop runtime and tool-attachment path, using browser-client.mjs, Browser plugin 26.820.60940, and the in-app Browser service as the available entry points. Reproduce after full restarts and new tasks, then verify that the trusted browser-control tool is exposed and that @Browser can list or inspect open tabs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- desktop, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100