Use it now Notable
Self-hosted gateway's database config adds a connect_timeout_seconds setting
What
The configuration schema for the self-hosted gateway's database connection pool gains a new field, connect_timeout_seconds. It accepts an integer between 1 and 60, defaulting to 5, and sits alongside the existing max_connections setting.
Why
This lets operators of a self-hosted gateway tune how long the database pool waits when establishing a connection, instead of relying on a fixed, unconfigurable timeout.
Names in the bundleconnect_timeout_seconds
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.
Confirmed since
Anthropic's documentation has since written up connect_timeout_seconds, on Claude apps gateway configuration.
| `connect_timeout_seconds` | No | Seconds the gateway waits when it opens a Postgres connection. A whole number from `1` to `60`, default `5`. Raise it if connection attempts time out when a new gateway instance starts. Requires Claude Co…claude-apps-gateway-config see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up connect_timeout_seconds, on Claude apps gateway configuration.