Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.295 ·

Gateway now warns clearly when its Postgres database is read-only

When the gateway's Postgres database cannot be written to, the gateway now logs a warning naming the cause and how to fix it

You'll notice Improvements
JSON All of v2.1.295
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
LLM GatewayArea: what it touches
ImprovementsKind: in v2.1.295,
ImprovementsSection of the release
What

The gateway can keep its data in a Postgres database, set with store.postgres_url. When that database is read-only, the gateway now logs a specific warning instead of a general one. A database is read-only when it is a standby copy, or when its default_transaction_read_only option is on. The warning says:

  • New sign-ins fail.
  • Spending is not recorded.
  • store.postgres_url should point at a database server that accepts writes.
  • The copy of the gateway should be restarted if the warning keeps appearing.

Before, this case showed up only as a general message that a cleanup step had failed.

Why

If you run the gateway, you now get a direct explanation for this failure and a fix, rather than a cleanup error that does not say what went wrong.

Read from
Names in the bundlestore.postgres_url

See this entry in the whole of v2.1.295 →

Feedback