Skip to content

the Computer pane drops the own-screen switch: every Bot on a shared computer is on its own screen - #210

Merged
hexuria merged 2 commits into
mainfrom
gol/always-own-screen
Oct 11, 2026
Merged

hexuria merged 2 commits into
mainfrom
gol/always-own-screen

Conversation

@hexuria

@hexuria hexuria commented Oct 10, 2026

Copy link
Copy Markdown
Owner

Client half of opengrok-server gol/own-screen-default (PR to follow).

The owner's call (11 Oct 2026): Bots that share a computer never share a screen. Every Bot gets its own screen, browser and Chrome profile, and the server drops PUT /coworkers/{id}/computer/screen and the use_own_screen tool. The pane's "Use its own screen" switch would do nothing, so this reverts #208.

A Bot can look at another Bot's screen with the server's new read-only look_at_screen tool. The app needs no change for it: the tool result's picture rides the existing tool-result image path.

Checks

  • cargo fmt --check, both clippy gates (-D warnings, default and --all-features)
  • cargo test --all-features: 1525 passed
  • Live: rebuild, relaunch against the updated server, and drive two Bots on one shared computer (pending, reported on this PR)

…computer is on its own screen

Reverts #208. The server now puts every Bot that shares a computer on a screen of its own, with
its own browser and profile, and has no route to switch it back (opengrok-server
gol/own-screen-default), so the switch would do nothing.
@hexuria
hexuria merged commit 3bcbc25 into main Oct 11, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant