Installation and Login

Most first-run problems fall into two buckets: the syntic command is not available after install, or authentication against api.syntic.ai fails. This page walks through the usual causes and how to clear them so you can get to a working session.

Installation problems

If your shell reports that syntic is not found after installing, the install location is probably not on your PATH. Confirm where the binary landed and make sure that directory is in your shell’s PATH, then open a new terminal so the change takes effect. If an old version keeps running, you may have two copies installed from different methods — remove the stale one so only the current binary is found.

Permission errors during install usually mean you are writing to a system directory without rights. Prefer a per-user install location over one that needs elevated privileges. After installing, run syntic --version to confirm the CLI is present and current.

Login and authentication

Syntic Code authenticates through api.syntic.ai. On first run it walks you through signing in and stores the resulting credentials locally under your .syntic/ configuration. If sign-in fails, check that your machine can reach api.syntic.ai — a proxy, VPN, or firewall that blocks it will stop authentication cold.

If you were signed in and are now being rejected, your stored credentials may have expired or become invalid. Sign out and back in to refresh them. Repeated failures with a valid account often point to a system clock that is wrong enough to break token validation, so confirm your time is accurate.

When it still will not work

Rerun the failing command with verbose output to see exactly which step fails and what the server returned. Note the exact message and your CLI version before seeking help, since those two details narrow the cause quickly.