{"version":"2.1.228","anchor":"gateway-token-endpoint-returns-404-when-its-flow-is-not-set-","canonical_anchor":"gateway-token-endpoint-returns-404-when-its-flow-is-not-set-","heading":"Gateway token endpoint returns 404 when its flow is not set up","tier":"internal","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/gateway-token-endpoint-returns-404-when-its-flow-is-not-set-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Gateway token endpoint returns 404 when its flow is not set up\n\nThe gateway's token endpoint returns a plain 404 when its flow was never set up.\n\n**What**\n\nIn 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.\n\n**Details**\n\n- Which configuration section supplies that component is not determined by the surrounding code\n\n**Evidence**\n\n`claude gateway requires the native binary. Install via https:\/\/claude.ai\/install.sh instead of npm.`\n\n- Area: Gateway\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}