Your apiKeyHelper output is now checked for junk characters and length before being used.
What's wrong with this entry?
If you use an apiKeyHelper script to supply your API key, its output is now checked for characters that cannot appear in a key and for a maximum length. Bad output makes Claude Code stop with an error telling you the script must print only the key. Previously any non-empty output was sent as-is.
- The rejection message is "apiKeyHelper output rejected: not a printable-ASCII token".
- Failure throws rather than falling back to an unauthenticated request, so a script that prints logs or a prompt alongside the key now fails loudly instead of causing a confusing auth error.
apiKeyHelper output rejected: not a printable-ASCII token
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Artifact tool now explains exactly which credential is blocking it
Both mention helper
-
v2.1.234
SDK reports where an API key actually came from
Both mention helper
-
v2.1.234
Signing back into the same account keeps a pending auto-resume
Both mention auth