The gateway's token endpoint returns a plain 404 when its flow was never set up.
What's wrong with this entry?
In the claude gateway server, a POST to /oauth/token now returns a plain 404 before parsing the form body if a component built earlier during server setup is missing. The gateway subcommand only runs on the native binary and throws otherwise.
- Which configuration section supplies that component is not determined by the surrounding code
claude gateway requires the native binary. Install via https://claude.ai/install.sh instead of npm.
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.227
claude gatewaynow identifies itself as the gateway providerBoth mention gateway
-
v2.1.229
Gateway streaming keeps connections alive with pings
Both mention gateway
-
v2.1.232
Cloud gateway sign-in explains its restart, and refuses when it cannot
Both mention gateway