Fleet oversight, project workspaces, and JAMES AI—one secure control center. Admin V2 stays untouched.
◇
Safe staging environment
Admin V2 remains the production control panel. This staging dashboard never runs admin write operations or changes your fleet.
ADMIN // FUNCTION REVIEW
Keep what works. Fix what doesn't.
Record each feature as working, broken, unused or untested. Nothing is deleted.
J
JAMES // AI COREServer1 brain · Server8 knowledge planned · Server9 worker planned
CONNECTING
J
JAMES // GRIDSHOCK AI
What are we building?
Ask about the DayZ panel, diagnose a screenshot, or generate a complete CAT script.
Files · screenshots · voice
JAMES proposes code; it cannot execute production commands. Voice recognition may use an external browser provider.
PROJECTS // FILE LIBRARY
Keep your project files together.
Drop source, logs, or screenshots below. Click a file to download it. Maximum 8 MB per file.
▧
Drag and drop files hereOr choose files using the upload button
READ-ONLY // DIAGNOSTICS
Know what's actually working.
Live local service states, private model tunnel status, and a clear separation between measured results and untested features.
Serverhub services
JAMES brain connection127.0.0.1:11435
⌘
SSH access required
Ollama is intentionally bound to Server1's loopback address. JAMES chat connects through a private SSH tunnel, never by exposing Ollama directly on the LAN.
GRIDSHOCK // KNOWN NODES
Fleet status.
Check SSH and agent TCP reachability across the known GridShock machines. No commands run on remote servers and no live server configuration is changed.
Not checked yet
A reachable TCP port is not proof that a service, login, game instance, or node agent is working.
GRIDSHOCK // LIVE SYSTEMD
Operations and security.
See measured Serverhub service states, including hosting, JAMES, DDoS protection, and background workers. Inactive does not automatically mean broken.
STATUS NOT CHECKED
Production actions still use your existing Admin V2 authentication. V3 does not bypass that login or run dangerous admin commands.
GRIDSHOCK // PRIVATE LOGIN
Account and access.
Change your V3 password without changing Admin V2 credentials. Changing it signs out all V3 sessions, including this one.
WINDOWS ACCESS: Use the SSH tunnel you configured for V3, then open http://127.0.0.1:18888. Root password SSH is not required. The V3 password never gets sent to JAMES or Admin V2.