Repository navigation
Φ Desktop Bridge R3: native governed Operator Desk - #66
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Build the promised real local operator interface on merged Desktop Bridge R0–R2, without silently granting desktop control to cloud agents or the existing Agentora web server.
Shipped
examples/desktop-bridge/operator-policy.example.json) with explicitobserve/clickBooleans, unknown app deny-by-default, strict schema, symlink and size restrictions.Critical boundary
Review is metadata-only. No R1 broker import, no agent-desktop execution, no API route, no network listener, no clipboard reads, and no autonomous action permission. Actual computer use still requires a separate human-controlled R1 session and a fresh, independently approved action.
Tkinter's confirmation dialog and the JSON review manifest are workflow controls, not OS-level identity or privilege boundaries. Windows ACL enforcement, IPC hardening and real Windows usability testing are future work.
CI
PYTHONPATH=server pytest -q server/tests/test_desktop_operator_desk.py; existing backend (Python 3.12 and 3.13) + web checks.Next rung
R4: OS-permissioned local IPC, task-level evidence verification, and supervised Windows field testing. Do not wire to the remotely callable
/api/actionsexecution path.