Connect clients
Validate the in-progress release-candidate path from a Nautilo client to its intended Server.
Deployment is finished only when the right person reaches the right Server. Do not test against a convenient browser tab and assume it belongs to the profile you just deployed.
Verify the active target
nautilo profile current
nautilo statusCheck the profile name, instance identity, and Server URL. Profile output is designed to remain secret-free.
Sign in
nautilo login
nautilonautilo login opens browser authentication on a workstation. Use
nautilo login --remote for device flow on a headless machine. The bare
nautilo command launches the terminal client.
The terminal client and any released desktop client must use the same Server URL. Mobile support remains in progress and is not a release-supported client path yet. A successful network connection is not enough: sign in as the intended owner, enter a Room, and make one model-backed turn.
Acceptance checklist
- The Server identity matches the selected profile.
- The owner login is known; no default or invented password is involved.
- Setup state is ready.
- At least one intended model route works.
- A second client, when used, reaches the same Room and durable history.
If the Server is fresh and unclaimed, stop. Return to the operator quickstart; do not silently create an unrecorded owner or wipe the deployment.