termdeck
The shell answers command not found when you run claude
Fix claude command not found in zsh, bash, PowerShell, CMD and Git Bash: where Claude Code installs, the PATH line for each shell, and stale npm shims.
Fixes
Fixes
One page per symptom, written from what the CLIs and the agents actually emit. Each one names the process that printed the line, because the fix for a shell error looks nothing like the fix for an engine error.
Claude Code
When Claude Code stops
A turn ends with Claude exited code 143
Exit code 143 is not a message, it is a signal number. What 143 and 137 each mean, who sends them, and which of the two means something actually broke.
A session you know exists is not in the list
A Claude Code session is filed under the exact text of the directory it started in. Four ways one project becomes two, and how to find the file anyway.
Claude Code logged you out or says your login expired
Log out of Claude Code with /logout or claude auth logout, switch accounts, and fix Login expired or a CLI that keeps asking you to log in again.
Claude Code uses an API key instead of your subscription
An API key wins over a subscription sign-in, and it can come from a settings file rather than your shell. Where to look, in the order the CLI reads them.
Codex CLI
When Codex CLI stops
Codex stops mid-task and says the usage limit is reached
Codex usage limit explained: the 5-hour and weekly windows, how to see what is left with /status, when it resets, and what credits or an API key change.
Codex refuses a model as not supported for the account
Fix the Codex error model is not supported when using Codex with a ChatGPT account: which models your login covers, retired models, and how to pick one.
Older Codex sessions are gone from the resume picker
Sessions that vanish from the Codex picker are usually still on disk. The three states one can be in, and the read-only command that reports which.
Codex keeps asking you to sign in again
A Codex login that keeps asking you to sign in is usually a rotated refresh token that two processes both tried to spend. What rotation means for backups.
Codex refuses a thread that already has a writer
Codex thread already has an active writer (code -32600): which client holds the thread, how to find it, and how to fork or resume the work safely.
Termdeck
Whichever engine you run
The agent installs cleanly and the machine never appears online
An agent that installed cleanly and never appeared is answering a 401, not failing to reach the network. Where the log says so, and the three causes.
The agent never asks before it edits or runs anything
A missing approval prompt is usually the mode doing its job. What each engine really enforces, which mode asks, and why one of them cannot enforce at all.
A machine that was working is now offline
A machine that has been running and drops off is a different problem from one that never connected. Four causes, in the order worth ruling them out.
The machine drops and reconnects over and over
Occasional reconnects are normal and self-healing. A machine that flaps every few seconds is one of three specific things, and two of them are yours to fix.
The connect code expired before the machine used it
A connect code is short-lived on purpose. What happens to the token behind it when it lapses, and why an install with an old code never connects.
The chat will not take input because something holds it
A chat that will not take input is attached to another process. Which holders can be taken over, which cannot, and what a forced takeover really does.
A turn ends because the machine disconnected
A link that drops mid-turn does not kill the work. The child keeps running on your machine for a few minutes, and the stream rebinds if the link returns.
Claude Code, Codex and Grok in one browser console