Run a Shared Server

A server holds one session; every client connected to it plays into that session. The flags are in the CLI reference; Sessions & Servers explains the model.

Start a server

resonon server --server-name "studio"

[server] Listening on 0.0.0.0:5555

It listens on every network interface, on port 5555, and announces itself on the local network under the name you gave.

Keep it to this machine

Bind to the loopback address:

resonon server --server-host 127.0.0.1

Require a password

resonon server --password "hunter2"

Or set RESONON_SERVER_PASSWORD, which keeps the password off the command line. When both are set, the environment variable wins; the startup line says which one is in force.

A server VSCode starts for you uses the resonon.server.password setting.

Join from VSCode

Open the RESONON sidebar. Servers on the local network appear in the Servers view on their own: click one to connect. For a server discovery can’t reach — another subnet, or UDP blocked by a firewall — choose Add Server… and enter its host and port.

A password-protected server asks for its password when you connect.

With several servers connected, Set as Active Server picks the one Cmd+Enter evaluates on.

Join from a terminal view

resonon view mixer --host 10.0.0.5 --port 5555 --password "hunter2"

Leave out --host and --port to pick a discovered server from a list.

Tell who ran what

Each client has a display name, shown in the status bar and next to its output. Set it with RESONON: Set Display Name or the resonon.client.name setting; without one, your system user name is used.

When several people evaluate at once, RESONON: Toggle Output Filter (Own / All) shows only your own output, or everyone’s.

Sessions & Servers — one session, many clients
VSCode Extension — every command and setting
Fix Connection Problems — when a connection fails