magnitude serve under a service wrapper; see Windows.
Install on the server
Run this on the server, over SSH if needed:magnitude server setup.
On macOS the installer installs the app without asking. Then run:
magnitude server setup afterwards. Run it as yourself, not with sudo: it asks for your password once, for the one step that needs it.
What setup does
magnitude server setup registers Magnitude as a service, turns on network access, creates a network access key, and prints how to reach the server:
magnitude status never shows it. Afterwards it is in Settings → Network access in the browser app on this machine, and setting the server up again keeps it.
- Linux
- macOS
Magnitude runs as the
magnitude.service systemd unit under its own magnitude system account. Its models, settings and logs live in /var/lib/magnitude, and its configuration in /var/lib/magnitude/config.json. Any account on the machine can run magnitude status, magnitude update and magnitude models right away; the models, settings and keys stay readable only by the service.Setup creates the magnitude account as a system account with no login. If the machine already has an account or group named magnitude that isn’t one, such as a person’s account, setup leaves it alone and stops without changing anything.Logs: journalctl -u magnitudemagnitude server setup again to finish once that’s fixed.
Check on the server at any time with:
Download a model
On the server:magnitude catalog status to check preparation, then request recommendations again. Magnitude loads the model on the first inference request. To load it ahead of time, run magnitude models load "MODEL_ID".
Or do all of this from the browser app on your laptop.
Use the app from your laptop
Openhttp://SERVER_IP:10100 in a browser on your laptop and sign in with the network access key. From there you can browse recommendations, download and load models, watch usage, and change settings. See Open the app from another device.
Connect from your laptop
Use these settings in your agent or app:
Use your agent’s configuration instructions, then check the connection from your laptop.
To use an agent on the server itself, connect it from your own terminal there:
localhost.
Updates
The server checks for updates about once an hour, downloads them, and installs them when no request or agent turn is running. Clients reconnect after a short pause. If an update needs something only you can do,magnitude status and the logs say so. To install a downloaded update right away, restart the server (sudo systemctl restart magnitude on Linux, sudo launchctl kickstart -k system/dev.magnitude.server on macOS); it installs the update as soon as it is idle. Running the install script again upgrades a Linux server in place; on macOS it asks you to remove the server first, since the server keeps itself up to date.
The desktop app on the same machine
The app and the server can’t run at the same time. Opening the app while the server runs shows a screen that offers to keep the server, which opens it in your browser instead, or to stop it and use the app. On Linux, stopping it from the app at your desktop needs no password; over a remote session, and on macOS, it asks for administrator authorization.Stop and remove the server
/var/lib/magnitude on Linux, now owned by root, or in ~/.magnitude on macOS. Run magnitude server setup again to bring the server back with the same models. If removal stops partway, run it again to finish.
Without the service
To serve only until you stop it, for example to try things out:nohup magnitude serve & keeps it serving after you disconnect, until the machine restarts; on macOS, closing the terminal stops it. Opening the desktop app stops it and takes over serving. Like the service, it installs downloaded updates between requests whenever it can without asking for a password: on Linux when sudo doesn’t ask you for one, on macOS when you can write to the Applications folder. Otherwise it prints a line saying the update is downloaded; stop it, run magnitude update install, and start it again. For network access without the service, see Network access.
Windows
Magnitude has no server mode on Windows;magnitude server setup explains this and changes nothing. To run Magnitude as a service, wrap magnitude serve with NSSM, as you might for Ollama. Download NSSM and use the full path to its nssm.exe (for example C:\nssm\win64\nssm.exe) wherever these steps say nssm, unless you put it on your PATH.
- Sign in as the account that will run the server and install Magnitude for Windows. The service must run as this same account: the installation is private to it, so other accounts, including
LocalSystem, can’t start it. This account doesn’t need to be an administrator. - Still signed in as that account, turn on network access: create or edit
%USERPROFILE%\.magnitude\config.jsonwith anetworkobject and a long, random key. All fields are in Configuration file.
- In an administrator PowerShell, register the service to run as that account. An administrator can do this from their own session: set
$accountto the account from step 1 (COMPUTERNAME\user, orDOMAIN\userfor a domain account) and$userProfileto its profile folder.magnitude servemust be started through the Magnitude command inMagnitude CLI, as below; the app’s ownresources\magnitude.exerefuses to serve.
Get-Credential asks for the account’s password in a prompt, so it isn’t typed on the command line or saved in your PowerShell history. Don’t write the password into the nssm set command itself. If the account’s password changes, run the Get-Credential and ObjectName lines again.
- If other computers need to reach the server, allow inbound TCP port 10100 in Windows Defender Firewall from the administrator PowerShell:
-Profile Private,Public only if you trust that network.
- Download a model. Models download through the running server, so do this once the service is running: use the commands in Download a model on the server, or the browser app from your laptop.
nssm stop Magnitude), run magnitude update install, then start it again. To remove the service, stop it first, then remove it; a running service keeps serving, including on the network, until it stops: