Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.282entry #12

Claude Code v2.1.282 ·

Self-hosted gateway: /readyz can stay ready through Postgres outages, plus a load-test mode

New store.readiness_grace_seconds keeps the gateway's /readyz ready through short Postgres outages, and a load_test_mode block serves canned replies

Group of 2 Use it now New Features
JSON All of v2.1.282
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Self-Hosted GatewayArea: what it touches
New FeaturesKind: in v2.1.282,
What probably matters to youSection of the release

Unclear It is not clear which Claude Code product or mode runs this server.

What

The self-hosted gateway is the server bundled in the CLI. It logs 'upstream requests' limits and serves /readyz, the address an orchestrator or load balancer checks to decide whether a copy of the server is ready for traffic. Before this release, /readyz returned 503 "store unavailable" whenever its check of Postgres (the gateway's database) failed, and it logged nothing. This release adds:

  • store.readiness_grace_seconds: a new config key taking a whole number from 0 to 3600, default 0. When it is above 0, /readyz keeps reporting ready for that many seconds after Postgres stops answering, then returns 503. During that time the gateway logs what happens to inference, which depends on enforcement.fail_closed_on_error (default false).
  • A warning at the default of 0: /readyz still returns 503 immediately, but now logs a warning recommending the new key.
  • load_test_mode: a new config block with enabled, reply_tokens (default 750) and reply_seconds (default 9.5). It serves canned replies instead of calling the upstream.

Why

To keep the gateway reporting ready through a short outage such as a database failover, set store.readiness_grace_seconds to more seconds than the outage lasts, up to 3600. Otherwise one Postgres blip can make every replica report not ready at once, and the load balancer or orchestrator may pull them all. Check enforcement.fail_closed_on_error to know how requests are treated during the grace period. The load-test mode lets you exercise the gateway without sending requests upstream.

Read from
Names in the bundlestore.readiness_grace_seconds
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Claude apps gateway spend limits touched a line naming store.readiness_grace_seconds after this was published. Fail-open only helps while your load balancer or orchestrator still routes traffic to the gateway. See [Outage behavior](/docs/en/claude-apps-gateway-deploy#outage-behavior) for `store.readiness_grace_seconds`, which keeps replicas passing… claude-apps-gateway-spend-limits see the edit
Confirmed since Anthropic's documentation has since written up store.readiness_grace_seconds, on Claude apps gateway deployment and operations. The gateway serves `GET /healthz` as a liveness probe and `GET /readyz` as a readiness probe. `/readyz` verifies the store is reachable. If you set [`store.readiness_grace_seconds`](/docs/en/claude-apps-gateway-config#store), `/readyz` kee… claude-apps-gateway-deploy see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which Claude Code product or mode runs this server.
Anthropic's documentation agreesAnthropic's documentation has since written up store.readiness_grace_seconds, on Claude apps gateway deployment and operations.
Anthropic's release notes agreeAdded store.readiness_grace_seconds to the Claude apps gateway so /readyz can stay ready through a short Postgres outage such as a database…

See this entry in the whole of v2.1.282 →

Feedback