termdeck
The shell answers command not found when you run claude
Why the shell cannot find the claude binary after an install that worked, where the file actually lands, and what changes when a service runs it instead of you.
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 looks signed out on an idle machine
A subscription token is refreshed only when the CLI itself runs, so a machine nobody has opened in a while can look signed out while its login is fine.
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
What the Codex usage limit really is, which of the two rolling windows you filled, when it lifts, and how to tell whether a reset credit is sitting unused.
Codex refuses a model as not supported for the account
The 400 is the backend refusing a model your login does not cover. Why the CLI let you ask for it, and how to see the list your account can really use.
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.
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.
Claude Code, Codex and Grok in one browser console