Unverified50% confidenceFactExact time
Before v2.1.314, claude -p would exit with code 0 and no output when startup failed; now it prints an error and exits with code 1.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/30/2026
First Seen
Valid until: 1/28/2027
Sources
Related Entities
Related Claims
UnverifiedConfiguration errors (such as a model name returning 401/403/404) should terminate the entire run within the first minute rather than being retried with backoff.68% similarUnverifiedBefore trusting an exit code of 0, you should first print the hostname, user, and executable path, because a green exit code on the wrong machine does not represent success in the expected environment.66% similarUnverifiedBoth types of unlearning implementation errors—multiplying by 0.0 short-circuit and replacing targets with wrong labels—will not trigger runtime errors or exceptions during code review.66% similarUnverifiedThe update fixes an issue where claude -p and Agent SDK sessions could hang without output after an internal error; they now report the error and exit with exit code 1.66% similarUnverifiedThe POSIX standard allows exit codes in the range 0–255; grep uses exit code 1 to indicate no match found and 2 to indicate an error occurred, while diff uses 1 to indicate files differ and 2 to indicate an error.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1114938API
curl https://kongchang.com/api/v1/knowledge/claims/1114938MCP
get_claim(id=1114938)