Sign in on a remote or headless machine
When Syntic Code runs on a server you reach over SSH, in a container, or on any computer without a browser, the normal browser sign-in cannot finish, because the browser has to return to the machine where syntic is running. Use the paste flow instead: you open the sign-in page on your own computer and paste the result back into the terminal.
Why the normal flow gets stuck
During a browser sign-in, the Syntic page sends you back to a short-lived address on the computer that started the sign-in. Over SSH or remote desktop, your browser and syntic are on different machines, so that hand-back never arrives and the terminal keeps waiting.
Use the paste flow
Start sign-in without a browser
On the remote machine, run:
SYNTIC_NO_BROWSER=1 syntic auth loginNo browser is opened. The terminal shows a sign-in address and waits for you to paste something back.
Open the address on your own computer
Copy the address into a browser on the computer in front of you. Log in to your Syntic account and choose Authorize.
Paste the result into the terminal
The page says Almost there and copies an authorization code to your clipboard (choose Copy code if it did not). Paste the code into the waiting terminal and press Enter. You are now signed in on the remote machine.
Check it worked
syntic auth statusFor servers that run without anyone at the keyboard
For CI jobs and scheduled tasks, signing in by hand on every run is not practical. Store a credential in your CI’s secret store instead. See API keys and environment variables.
Treat anything you paste during sign-in like a password. Do not post it in chat tools or tickets. If you think it leaked, sign out with syntic auth logout and sign in again.