Skip to content

Harden VM health, simplify desktop access, and prepare a responsive relay - #16

Open
benjaminshafii wants to merge 2 commits into
mainfrom
fix/runtime-health-and-vnc
Open

benjaminshafii wants to merge 2 commits into
mainfrom
fix/runtime-health-and-vnc

Conversation

@benjaminshafii

Copy link
Copy Markdown
Member

Summary

  • Verify Lume runtime process identity/config ownership instead of trusting stale inventory; fail closed for dead, reused, zombie or unverified processes, and invalidate cached inventory after lifecycle completion.
  • Parse timestamped informational Lume stdout safely so a completed shutdown is not falsely reported as failed or replayed.
  • Add an opt-in persistent graphical upstream owner plus an RFB relay. Human reconnects/encoding negotiation terminate at the relay, credentials are separate, and lost upstreams are quarantined without reconnecting into the same VM process.
  • Require pinned guest SSH and optional console readiness before startup success; expose console health independently from compute.
  • Package optional Python dependencies/LaunchAgent setup, failure/drain procedures and agent/Screen Sharing onboarding.
  • Streamline the control UI; add explicit POST+CSRF-protected human desktop-password access and HTTP clipboard/manual-copy fallback.
  • Prepare relay performance changes: per-viewer incremental regions, negotiated zlib, a separate screen writer to keep input responsive, and a configurable 15 FPS target cap. Add a repeatable synthetic bandwidth benchmark. These changes are not deployed; a coordinated maintenance window and new real-Mac acceptance run are required.
  • Publish a sanitized real-Mac acceptance report; no credentials, deployment identities, private addresses, raw logs, captures or disks.

Validation

  • JavaScript tests: 111 passing.
  • Python relay unit tests: 40 passing locally and in an isolated preparation directory on the Studio's Python 3.12 runtime. The running relay was not replaced or restarted.
  • Synthetic loopback fixture: 15 small-region updates transferred 5,368 bytes with negotiated zlib vs 124,416,240 bytes with the old raw full-frame relay. This is a flat-color generated fixture, not a real-world latency/video or deployed-speed claim.
  • Publication hygiene and diff whitespace checks: passing.
  • Private deployment: 45.46-minute measured two-VM acceptance window (52.40 minutes total runner duration), including 83 desktop connections/captures, 12 starts, 12 graceful stops, 3 explicit forced stops, 4 creates/deletions, command/file checks, and persistence after a deliberate runtime exit. Zero new Lume crash reports or relay upstream failures.

Limits / review notes

  • The real-Mac result covers the private deployment, not a clean installation of this public reference.
  • Additional duplicate-owner, downstream-resize and performance hardening is unit-tested but is not included in that completed soak.
  • User explicitly selected preparation only: do not deploy by hot-restarting the persistent owner or interrupt either current VM.
  • Desktop remains off by default; MCP remains loopback by default. No public/Funnel endpoint is introduced.
  • Native VNC listeners still need network containment; per-VM authorization and hostile-guest isolation remain out of scope.
  • Not a release, uptime guarantee, snapshot implementation, or clean-machine bootstrap certification.

Related: #2, #6, #12, #14. These broader roadmap items are not closed by this PR.

@benjaminshafii
benjaminshafii marked this pull request as ready for review October 17, 2026 05:08
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