Troubleshooting

Errors print one line to stderr, prefixed Error:, and exit 1. Most say what to do next; the cases below are the ones that do not.

Start with sim whoami. It prints the resolved endpoint, workspace, and output format, and where each came from — which explains most surprises on its own.

A command targets the wrong workspace or deployment

Each setting resolves independently, and a flag beats the environment, which beats the profile. A stale SIM_WORKSPACE in your shell silently outranks the workspace you configured.

sim whoami

Note that sim login sets the profile's default workspace to whichever one you picked on the approval page. It does not limit the key to that workspace — use --workspace to reach any other workspace the key can access.

An error ends in — run: sim login --profile <name>

The API rejected the key with a 401. Either it was revoked, or it belongs to a different deployment than the endpoint you are pointed at — a key minted against a local stack will not authenticate against production. Check the endpoint before re-authenticating:

sim whoami --profile <name>

Could not reach https://sim.ai: <reason>

The request never got a response: DNS, TLS, a proxy, or a self-hosted stack that is not running. Confirm the endpoint the CLI actually used with sim whoami, and that it has the right scheme and port:

sim configure --set-endpoint http://localhost:3000 --profile local

A JSON flag rejects a value that looks like valid JSON

Your shell consumed the quotes. Wrap the whole value in single quotes, or read it from a file:

sim tables rows query tbl_123 --filter '{"all":[{"field":"status","op":"eq","value":"open"}]}'
sim tables rows query tbl_123 --filter @filter.json

A value looks truncated

table clips long cells to keep rows on one line. The data is not truncated — switch to a machine format to see it in full:

sim logs get run_123 --output json

sim files get refuses to print to the terminal

Writing arbitrary binary to an interactive terminal can corrupt it, so non-text content has to go to a file or a pipe:

sim files get file_123 -o ./image.png
sim files get file_123 | shasum

A stored output format is invalid

A higher-priority source still wins, so you can repair the profile without editing the file by hand:

sim --output table configure --set-output json

Anything else

An unexpected error prints a stack trace. That is a bug in the CLI — please open an issue with the command you ran, the trace, and the output of sim --version.