System
Connections, updates and recovery for your home setup.
Loading connections…
Connection addresses
Owner access
Owner approval
Use your existing Luma hub password to sign in and approve connection changes.
Temporary maintenance access
Ubuntu connection & setup
Ubuntu VM
Already have Agent Zero? Inspect its properties first. Reusing an existing container needs a compatibility review; Create separate Luma A + B creates its own containers.
The installer creates separate data folders and local model services. It never mounts the host filesystem or Docker socket inside Agent Zero. Existing VM workloads stay in place.
Updates & commands
Ubuntu updates & commands
Install connector updates and run Ubuntu commands from this app.
Enter your hub password or active secondary admin passcode in Owner approval above, then unlock. The first installation of connector 3.5.0 enables these controls.
Choose 30 minutes to 30 days. Thirty days is a fixed duration, not a calendar month.
This unlock never extends your sign-in or temporary maintenance access. Lock tools at any time. Changing the choice applies only to your next unlock.
Locked.
Agent A in your browser
Open Agent Zero’s own interface on home Wi-Fi to test a new chat directly.
Install connector 3.5.10 to enable HTTPS browser access.
Port 9444 uses a local HTTPS certificate. Check the displayed fingerprint if your browser asks you to accept it. A welcome message alone does not confirm a task response.
Certificate fingerprint
Connector update
Finish agent tasks before installing. Installation continues through the connector restart. Select the same file again to resume an interrupted upload.
Ubuntu terminal (via connector)
Commands run on the Ubuntu VM. Output appears here and is not added to project chats. This panel does not accept interactive password prompts or terminal applications.
Choose the conversation ID shown in your project's Local AI settings.
Checks the chosen project's saved model settings and tool definitions. Review the script, then tap Run command.
Search command history and exports. Completed history no longer blocks new commands after the Ubuntu companion is installed.
Use the administrator option for commands that need root. Commands needing confirmation should include their non-interactive flags, such as apt-get -y.
Direct Agent A chat
Agent Zero A · collaboration
Use letters, numbers, hyphens or underscores. A’s messages and files can be shared with your cloud team.
Replies refresh automatically while this screen is open.
NAS storage A
NAS storage A
Use the NAS storage A code from sudo luma-vm codes on Ubuntu. Configure storage before creating the new A/B containers.
A0A · AgentzeroA on your configured NAS. Shared files use A0A/luma/files; local model copies use A0A/luma/models.
These storage controls require your hub password. Configure B storage only inside Android Private. After Ubuntu reboots, connect each NAS storage again to start its agents. Existing local deployments need a separate migration.
Private gateway setup
Private NAS gateway
Private B has its own port, PIN, session and storage. Set this up from home. Keep port 8788 out of Cloudflare, nginx and router forwarding.
In Android choose Private. Paste this gateway code and the separate NAS storage B code from Ubuntu, then set a private PIN of at least 8 characters. You can pair Agent Zero B after deployment. Never paste B’s code into a normal chat.
Agent Zero A · live view
View-only desktop · about one frame per second. The desktop is shared by conversations on A; the activity log follows the project ID below.
Connecting…
Tool and command activity
Latest 200 events; long output is shortened. Desktop frames are not recorded or attached to chats.
Ubuntu setup activity
Tracks Luma’s installer steps and errors. Commands run independently over SSH are outside this log.