Error Reference

This page lists the errors you are most likely to see from Syntic Code, what each one means, and how to resolve it. Errors are grouped by where they come from — authentication, network, the filesystem, and command execution — so you can jump to the right category. When an exact message is not listed here, rerun with verbose output to see the underlying detail.

Authentication errors

Messages about being unauthorized, having invalid credentials, or a session that expired all mean the same thing: Syntic Code could not prove your identity to api.syntic.ai. Sign out and sign back in to refresh your stored credentials. If it recurs immediately, confirm your account is active and that your system clock is accurate, since a badly wrong clock breaks token validation.

Network and connection errors

Timeouts, connection refused, and “could not reach the server” point at the path between your machine and api.syntic.ai. Check your general connectivity first, then any proxy, VPN, or firewall that could block the endpoint. Rate-limit messages mean you are sending requests faster than allowed; wait briefly and retry, and avoid tight automated loops that hammer the API.

Filesystem and permission errors

Errors about a file not being found usually mean a path was mistyped or the file was moved — confirm it exists from your shell. Permission-denied errors mean the process cannot read or write where it is trying to; check the ownership and mode of the target, and avoid working in directories that require elevated privileges.

Command execution errors

When a shell command Amara ran fails, the error you see is the command’s own output, not a Syntic Code fault. Read that output directly and ask Amara to interpret and address it. A non-zero exit code simply means the command reported failure; treat it as you would if you had run the command yourself.