You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: "Open in BiBCode browser" on a chat link does nothing; system browser works #210
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
Not sure
Steps to reproduce
In a project chat, get an agent reply that contains an https:// link.
Click the link. A menu opens with Open in BiBCode browser, Open in system browser and Copy link.
Click Open in BiBCode browser.
Repeat steps 2–3 a few times.
Click the link again and choose Open in system browser.
Expected behavior
Step 3 opens the URL in BiBCode's built-in browser panel.
Actual behavior
Step 3: the menu closes and nothing else happens. No browser panel opens, no tab is created and no error or toast appears. It failed the same way three times in a row in my recording.
Step 5: the same URL opens normally in the system browser, so the link itself is fine and only the built-in browser path fails.
Impact
Minor bug or occasional failure
Version or commit
0.13.0
Environment
Windows 11 Pro 10.0.26200 (x64), desktop app, Claude Code 2.1.310 provider
Logs or stack traces
# Preview state queried through the BiBCode preview MCP tool (preview_status) right after the failed clicks:
{"available":true,"loading":false,"tabId":null,"title":null,"url":null,"visible":false}
# userdata/logs/server.log has no entry at all for the time of the clicks# (last line about 14 minutes earlier), so the action seems not to reach the server,# or fails without logging.
Screenshots, recordings, or supporting files
A 13 s screen recording is available on request (it shows internal content, so I did not upload it).
Triage, 2026-10-31. Not going into PR #213 (#139 MCP batch). It goes in a follow-up PR after that release. Batch 6. It needs a Windows reproduction first (the report is Windows 11 x64, 0.13.0), with the web console and server log captured at the click.
Activity
mubeda commentedon Oct 31, 2026
Triage, 2026-10-31. Not going into PR #213 (#139 MCP batch). It goes in a follow-up PR after that release. Batch 6. It needs a Windows reproduction first (the report is Windows 11 x64, 0.13.0), with the web console and server log captured at the click.
Planned order after the release: (1) #222 copy lint; (2) quick fixes #228, #221, #229, #231, #232; (3) MCP #220; (4) performance #225, then #223, #226, #227; (5) features #230, #224, #211, #212; (6) #210 after a Windows repro.
test(web): mock the thread load state in the ChatView hooks tests (#210)
Merge remote-tracking branch 'origin/v015b/210-open-in-bibcode-browse…