Bot browsing on a remote machine can't be watched: the machine's screen takes the browser's place
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 74/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- react, typescript
- Área
- frontend
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 277
- Forks
- 27
- Merge medio
- 2 h 47 min
- PR fusionados (30 d)
- 1
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de DuskBotAI/duskbot
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
Los mantenedores suelen responder en 1 día
-
After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 pageAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
install.sh --tailscale replaces whatever the host already serves on tailnet port 443Posiblemente ocupada @viniciusbregoli la tomó hoy. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
Todos los issues de DuskBotAI/duskbot
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vercel-labs/ui#865 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
outline/outline#14638 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
wayfinder:grilling
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
patricktree/cup#484 ·
-
bot:ai-assisted component:platform-js status:untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
midnightntwrk/platform-js#69 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 1 día