Sign in to Syntic Code
Syntic Code signs in with your Syntic account through your web browser. You do it once; after that the CLI keeps you signed in by renewing its access in the background, and there is nothing to copy or paste.
Sign in
Start the sign-in
Use whichever fits where you are:
| Where you are | What to do |
|---|---|
Starting syntic for the first time | Choose Sign in on the welcome screen. |
| In your shell | Run syntic login (or syntic auth login). |
| Inside a session | Type /login. |
Approve in the browser
Your browser opens a Syntic page. If you are not logged in yet, choose Continue with Google, or enter your email and choose Continue with email to get a one-time code.
The page then asks Authorize Syntic Code CLI? and lists what the CLI may do, such as use Syntic models on your behalf and count toward your plan’s usage. Check the Signed in as line at the bottom, then choose Authorize. If it shows the wrong account, choose Switch account first. If you belong to more than one organization, you may be asked to pick the one to connect.
Go back to the terminal
The browser shows a short confirmation that you can close the window. The CLI notices the approval on its own and finishes signing in. Your plan name appears on the Plan: line at the top of the session.
If the browser does not open
/login also prints the sign-in address. Type /login copy to put it on your clipboard, then paste it into any browser on the same computer.
If you are working on another machine over SSH, or on a computer with no browser, use the paste flow instead. See Sign in on a remote or headless machine.
Confirm your sign-in
syntic auth statusIt shows logged in : yes or no. The command also exits with code 0 when you are signed in and 1 when you are not, so scripts can check it. Inside a session, /status shows your account, plan and model.
How your sign-in is kept
- Syntic Code does not create a long-lived API key for you. It holds a short-lived access token and a refresh token, and swaps them for new ones before they expire.
- Credentials are stored in your user folder and can only be read by your own user account.
- A project you clone can never choose your credentials or redirect your sign-in, because project settings files are not allowed to set them.
- Commands, hooks and plugins that Syntic Code runs for you do not receive your credentials.
Syntic Code needs a paid plan. If your account is on the Free plan, signing in works in the browser but the CLI then refuses with “Your account is a free one. Please upgrade to use Syntic Code.” See Use Syntic Code with your individual plan.
Work accounts
Your company can limit sign-in on its machines to its own organization. If a sign-in with your personal account is refused on a work computer, sign in with your work account instead, or ask your administrator.
Learn more
- Sign out or switch accounts
- Syntic Code sign-in loop
- API keys and environment variables
- Sign in, in the Syntic Code docs