---
title: Troubleshooting
description: "Fixes for common TheGitAI problems: sign-in failures, model errors, stuck background jobs, and recovering an interrupted session."
---

# Troubleshooting

Most issues come down to auth or account state. Here's where to start.

| Symptom | Fix |
|---------|-----|
| **"Not signed in"** | Run `ai` — it shows the sign-in screen and then starts your session. |
| **Auth or permission errors** | Run `ai whoami` to confirm the signed-in account. |
| **Usage or quota errors** | Run `ai --usage` to check your remaining usage and reset time. |
| **Signed in with the wrong account** | Run `/logout` (or `ai logout`), then `ai`, and sign in as the intended account. `ai login` no longer re-prompts while signed in, so signing out is how you switch. |
| **Local session was used with a different sign-in** | The session and its history are still yours and remain on this computer. To continue it, sign in with the TheGitAI account you used for that session or start a new session. Contact `support@thegit.ai` for an accidental duplicate account. |
| **`stdin` or `stdout` is not a terminal** | Run coding sessions directly in an interactive terminal; piped one-shot coding is not supported. |

## Anything else

Re-run the command, then file the printed error message with `/report` — it
opens the [public issue tracker](https://github.com/thegitai/thegitai-cli/issues/new)
in your browser. There is **no client-side debug mode by design** — the
printed error is the source of truth for what went wrong.

::tip
When in doubt, `ai whoami` followed by `ai --usage` answers most "why isn't this
working" questions in two commands.
::