feat: machine nodes — NyxBot and specialists use the owner's machines; NyxBot features move to the assistant workspace (0.40.0) - #1722
Merged
Conversation
added 5 commits
October 1, 2026 09:34
… (shell, files, git through connected services, live desktop, saved logins)
…ental consent) into nyxbot/machine-nodes
…eover preemption, sandboxed browser, native live desktop, assistant workspace placement
📊 Code coverage
Gate: line coverage must stay at or above the threshold. Ratchet plan (W21): Backend → 55%, CLI → 50%, Frontend → 30% by quarter end. |
…, read-only permissions for machine container CI job
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.
Summary
NyxBot and its specialists can use the owner's machines (a host, a remote VM or a container) through credential nodes. They can run commands, edit files, use git and SDKs through the owner's connected NyxID services, and operate the desktop and browser with cua-driver. The owner can watch live, take over and hand back. Version 0.40.0.
shell,files(confined to workspace roots, TOCTOU-safe opens) andcomputer(cua-driver);nyxid node setupfor one command, thenyxid-node-machinecontainer image (Xvfb, Chromium, cua), and--separate-usersVMs.machine_confirm(none,changesorall) uses action cards. Webhook automations add their confirmation policy on top.insteadOfcome from a server-generated, catalog-driven environment spec.nyx__machine_fill_logintypes through a force-installed filler extension and a native messaging host: origin and field checks, password-type pinning, TOTP computed in NyxID, output scrubbing.PR_SET_NO_NEW_PRIVSand a seccomp filter that denies namespace creation.nyxid__machine_setup_linkandnyxid__machine_pair; registration tokens never enter chat; NyxBot wakes when the machine connects./assistant/*with assistant-sidebar entries./automationsredirects with its parameters preserved.Performance (D17)
macOS desktop numbers need Screen Recording and Accessibility permissions; the repeatable command is in
docs/MACHINE_NODES.md.Rollout
Upgrade the backend first, then nodes. Machine features are opt-in on each node. No new required environment variables.
Verification
-D warningsclean.NoNewPrivs, namespace denial, git and desktop.docs/MACHINE_NODES.md.