Bot browsing on a remote machine can't be watched: the machine's screen takes the browser's place
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 74/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start in src/components/bot-panel/ComputerTab.tsx and src/components/ComputerPanel.tsx, tracing how the machine screen and browser panel are selected for a bot running on a paired server. Check the browser stream client and the stated panel behavior for guidance. Done means a bot with browsing enabled can view its live browser from the server's page while retaining access to the machine screen.
Written by the indexing model from the issue text.
Description
What happened
A bot that browses on a remote machine (a paired server of your own, or My Cloud) keeps browsing, but the panel never shows it: the machine's screen takes the browser's place.
On This computer the Computer tab shows the bot's live browser — the page, its tab strip (LocalBrowserSection, src/components/bot-panel/LocalBrowser.tsx) — because the page is this computer's. On the server's page it shows that machine's screen instead, and the Browser tab is not in the tab row either.
Where the panel decides:
src/components/bot-panel/ComputerTab.tsx:314—ownScreen = !local || cloudOwned || current === "vm", withlocal = isLocalHost(runsOnHost(...))(:187,:304).runsOnHostreadsotherServerfrom the desktop (src/lib/other-server.ts), so a window on a paired server comes out askind: "vps",localis false, and the screen renders in place of the browser section.src/components/ComputerPanel.tsx:275-278— the Browser tab exists only when the bot's computer is"browser"or the stored view for that bot says browser;src/lib/computer-panel-view.tsresolves any other stored view to"computer", and the stored view is per origin, so a Browser tab chosen on This computer does not exist on the server's origin.- The bot's browser still mounts on whichever server runs the turn. It is gated only on
features.browser,bot.browser !== false,bot.computer !== "off"and not the person's own Chrome (server/host/browser.ts:316,:404), and it is streamed at/api/bots/<id>/browser(src/lib/browser-stream-client.ts), so the server's page could render it.
So the browsing is real — its tool lines appear in the chat — but there is no live view of it.
Verified
- DOM test against the real
ComputerPanel: a bot withcomputer: "local"andfeatures.browseron has nocomputer-panel-tabs-tab-browserand no browser panel;computer: "browser"shows both. (Temporary test, deleted after the run.) computerPanelTabs({ browser: false })→["computer"];resolveComputerPanelView("browser", { browser: false })→"computer".runsOnHost({ cloudHome: false, otherServer: "box-1", platform: "darwin" })→{ kind: "vps" }, whichisLocalHostrejects, soownScreenis true.
Steps to reproduce
- Pair a server of your own (or move a bot to My Cloud) and leave its browsing on.
- Set the bot's computer to that machine, not "Browser only".
- Open the bot's Computer tab with the window on the server: no Browser tab (unless it was chosen earlier on that origin), and the machine's screen where This computer shows the bot's live browser.
- Give the bot a task that browses: it works — browser tool lines land in the chat — but the page is nowhere in the panel.
Version
0.2.17
Platform
macOS
Engine
No response
Logs or screenshots
Expected: a bot's browser is watchable wherever the bot runs.
Fix direction, not a decision: render the bot's browser section above the machine's screen whenever
`bot.browser !== false` and a browser is open (the stream route is the current origin's, so it already
works from the server's page), or keep the Browser tab in the row for every bot with browsing on
instead of only `computer === "browser"` ones.
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 27
- Avg merge
- 2h 47m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 DuskBotAI/duskbot
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 pageOpen
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
install.sh --tailscale replaces whatever the host already serves on tailnet port 443Possibly taken @viniciusbregoli claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in DuskBotAI/duskbot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patricktree/cup#484 ·
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day