First run

Signing in

The first launch is the only time AUTO/PILOT insists on a network connection. It asks for the email and password of your account on this site, then:

1. Verifies your credentials and that your email address is confirmed.
2. Generates a random device token locally and registers it, claiming one activation slot. The server only ever stores a hash of that token.
3. Receives a signed license token and caches it on disk.

From that point on the app verifies the cached license locally. No network, no phone home, no check-in — see licensing & offline behaviour.

If sign-in fails, the message tells you which of these it was:

Message	Meaning
INVALID_CREDENTIALS	Wrong email or password.
EMAIL_NOT_VERIFIED	Confirm your address on the website first.
LICENSE_REQUIRED	The account has no license pack. Buy one in the store.
ACTIVATION_LIMIT_REACHED	All slots are in use — free one or buy another pack.
ACCOUNT_DISABLED	Contact support.

Naming the device

The app suggests your machine's hostname. Change it to something you will recognise in a list six months from now — booth-mbp, backup-laptop, studio-desktop. This name is what appears on your dashboard when you need to free a slot in a hurry.

Your first route

1. Open Mappings → New route.
2. Click Learn, then move a control on your hardware. AUTO/PILOT captures it.
3. Pick a destination — a MIDI CC, an OSC address, an Art-Net channel, an internal macro.
4. Set the response curve if the default linear mapping feels wrong.
5. Save. The route is live immediately.

Your first scene

Scenes recall a whole rig state at once:

1. Get the rig into the state you want — routes enabled, macros armed, values set.
2. Scenes → Capture current state.
3. Name it after the moment, not the settings: drop_b, ambient_intro, panic.
4. Bind the scene to a pad so you can recall it without looking.

Scenes are what make a set repeatable. Build them at home, trigger them in the dark.