Syntic Code sign-in loop
If the browser opens and you approve, but the terminal keeps waiting, or Syntic Code asks you to sign in again and again, the sign-in result is not reaching the CLI or a different credential is getting in the way. The fixes below cover almost every case.
The terminal keeps waiting
| Cause | Fix |
|---|---|
| You did not finish every step in the browser | Make sure you chose Authorize and saw the confirmation page. |
| The browser is on a different computer (SSH, remote desktop, container) | The browser cannot return to the remote machine. Use the paste flow: run SYNTIC_NO_BROWSER=1 syntic auth login. See Sign in on a remote or headless machine. |
| The wrong browser opened | Type /login copy to copy the sign-in address, and open it in your usual browser on the same computer. |
| A browser extension or security tool blocks the return to your computer | Try a private window with extensions off, or a different browser. |
If the page says Authorization failed, run syntic login (or /login in a session) to start a fresh sign-in. “Invalid authorization request” means the same: start again from the terminal.
You are asked to sign in again and again
| Message | Fix |
|---|---|
”Your session has expired. Run syntic login to reconnect billing.” | Your sign-in was ended or could not be renewed. Run syntic login. |
”Not signed in. Run syntic login in a terminal to sign in (or set SYNTIC_API_KEY), then run this command again.” | No credential was found. Sign in. |
| Sign-in succeeds, then requests are refused with “Your account is a free one…” | Signing in worked, but the account has no paid plan. See Use Syntic Code with your individual plan. |
| Sign-in succeeds, then requests are refused with “Your plan isn’t active…” | Update your billing, then send your message again. See Payment declined or card failed. |
| A sign-in to your personal account is refused on a work computer | Your company limits sign-ins to its own organization. Use your work account. |
Check which credential is used
A key in your shell wins over your browser sign-in. Run /doctor in a session to see where the credential came from and when it expires. If an old key is set in SYNTIC_API_KEY, remove it (unset SYNTIC_API_KEY) and remove it from your shell profile too.
Start over
syntic auth logout
syntic auth loginThen check with syntic auth status.
Refusals because of your plan are never fixed by signing in again. Fix the plan or payment in the browser first, then send your message again.