Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One capture · claude-code

One read of Claude Code CLIclaude-code-20260925T033701Z

4 pages moved out of 210 read.

Pages moved 4 significant first
Pages read 210 in this capture
Captured 03:37 UTC
Corpus hash 2d5252e0ee53 corpus-hash

What this read moved

1-4 of 4

claude-apps-gateway-config Changed · +37 / -0 lines

### `load_test_mode`

from line 31
3131* [`managed`](#managed): managed settings policies by IdP group
3232* [`telemetry`](#telemetry): OTLP forwarding to your observability stack
3333* [`access_control`, `limits`, `timeouts`, `rate_limits`](#http-tuning): IP allow/deny, request size caps, upstream time-to-first-byte, and per-IP sign-in limits
34* [`load_test_mode`](#load_test_mode): load test the gateway without calling a model provider
3435 
3536## Secret expansion
3637 
from line 952
951952 
952953Behind such a front end, set [`listen.trusted_proxies`](#listen) first so the gateway sees real client addresses, and keep the gateway and everything in front of it unreachable from the public internet regardless.
953954 
955### `load_test_mode`
956 
957The `load_test_mode` block lets you load test a gateway without calling a model provider. While it's on, the gateway builds and signs each provider request as usual, discards it instead of sending it, and streams a canned reply back through its normal response path. The reply is filler text that begins with a sentence saying it is canned.
958 
959Requires v2.1.283 or later. Earlier versions refuse to start when the key is set, so upgrade every replica before you add the block and remove it before you roll back.
960 
961The example below turns the mode on with the defaults, a reply of 750 output tokens streamed over about 10 seconds:
962 
963```yaml theme={null}
964load_test_mode:
965 enabled: true
966 reply_tokens: 750 # roughly how many tokens of text each canned reply carries
967 reply_seconds: 9.5 # how long a streamed reply takes
968```
969 
970| Field | Required | Description |
971| --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
972| `enabled` | Yes | `true` turns the mode on. `false` keeps your numbers in the file with the mode off. The gateway refuses to start if the block is present without it. |
973| `reply_tokens` | No | Default `750`. Roughly how many tokens of text each canned reply carries, a whole number from 1 to 100000. |
974| `reply_seconds` | No | Default `9.5`. How long a streamed reply takes, from 0 to 600. `0` sends the whole reply at once. A reply to a non-streaming request always comes back at once. |
975 
976A load test in this mode covers the gateway, your Postgres, and everything in front of the gateway. It doesn't cover the provider's limits, speed, or network path.
977 
978While the mode is on, a request can carry an `x-load-test-user` header holding a whole number of up to seven digits, and the gateway counts each number as a separate developer with the email and groups of the developer whose token came with the request. Give the load-test deployment its own empty database, because the gateway refuses to start with the mode on against a database in which any developer has already spent anything.
979 
980<Warning>
981 Never turn this on for a gateway that developers use. Every request gets the canned reply and no model is called. The gateway logs a `load_test_mode is on` warning at boot and marks each `inference` [audit event](/docs/en/claude-apps-gateway-deploy#logs) with `load_test: true` while the mode is on.
982</Warning>
983 
954984## Complete example
955985 
956986This full reference config exercises every core section; the [HTTP tuning blocks](#http-tuning) keep their defaults. Copy it, delete what you don't need, and fill in your values. The config in the [Quickstart](/docs/en/claude-apps-gateway#quickstart) is a minimal version of this.
from line 1049
10191049 
10201050# enforcement:
10211051# fail_closed_on_error: false
1052 
1053# Load test this deployment without calling a model provider. Never on a
1054# gateway that developers use: every request gets a canned reply.
1055# load_test_mode:
1056# enabled: true
1057# # reply_tokens: 750
1058# # reply_seconds: 9.5
10221059 
10231060# Meter at contracted rates instead of USD list price. Requires admin: or a
10241061# managed: policy. With managed:, the same rates also go to signed-in clients.

platforms Changed · +9 / -9 lines

from line 25
2525 
2626Integrations let Claude work with services outside your codebase.
2727 
28| Integration | What it does | Use it for |
29| :----------------------------------- | :--------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------- |
30| [Chrome](/docs/en/chrome) | Controls your browser with your logged-in sessions | Testing web apps, filling forms, automating sites without an API |
31| [GitHub Actions](/docs/en/github-actions) | Runs Claude in your CI pipeline | Automated PR reviews, issue triage, scheduled maintenance |
32| [GitLab CI/CD](/docs/en/gitlab-ci-cd) | Same as GitHub Actions for GitLab | CI-driven automation on GitLab |
33| [Code Review](/docs/en/code-review) | Reviews every PR automatically | Catching bugs before human review |
34| [Slack](/docs/en/slack) | Responds to `@Claude` mentions in your channels | Turning bug reports into pull requests from team chat |
35| [Claude Tag](/docs/en/claude-tag) | Runs `@Claude` as your organization's shared identity with admin-configured access | Shared team access on Team and Enterprise plans, instead of per-user Slack sessions |
28| Integration | What it does | Use it for |
29| :----------------------------------------------- | :--------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------- |
30| [Chrome](/docs/en/chrome) | Controls your browser with your logged-in sessions | Testing web apps, filling forms, automating sites without an API |
31| [GitHub Actions](/docs/en/github-actions) | Runs Claude in your CI pipeline | Automated PR reviews, issue triage, scheduled maintenance |
32| [GitLab CI/CD](/docs/en/gitlab-ci-cd) | Same as GitHub Actions for GitLab | CI-driven automation on GitLab |
33| [Code Review](/docs/en/code-review) | Reviews every PR automatically | Catching bugs before human review |
34| [Slack](/docs/en/slack) | Responds to `@Claude` mentions in your channels | Turning bug reports into pull requests from team chat |
35| [Claude Tag](https://claude.com/docs/claude-tag) | Runs `@Claude` as your organization's shared identity with admin-configured access | Shared team access on Team and Enterprise plans, instead of per-user Slack sessions |
3636 
3737For integrations not listed here, [MCP servers](/docs/en/mcp) and [connectors](/docs/en/desktop#connect-external-tools) let you connect almost anything: Linear, Notion, Google Drive, or your own internal APIs.
3838 
from line 71
7171* [GitLab CI/CD](/docs/en/gitlab-ci-cd): the same for GitLab
7272* [Code Review](/docs/en/code-review): automatic review on every pull request
7373* [Slack](/docs/en/slack): send tasks from team chat, get PRs back
74* [Claude Tag](/docs/en/claude-tag): run `@Claude` as your organization's shared identity on Team and Enterprise plans
74* [Claude Tag](https://claude.com/docs/claude-tag): run `@Claude` as your organization's shared identity on Team and Enterprise plans
7575 
7676### Remote access
7777 

claude-apps-gateway-deploy Changed · +1 / -1 lines

from line 191
191191* **[Spend-limit enforcement](/docs/en/claude-apps-gateway-spend-limits#postgres-availability)**: fails open by default during the outage, so inference still flows; flip it to fail closed if you'd rather block than run unmetered
192192* **Readiness**: `/readyz` reports not-ready during the outage, so orchestrators that gate traffic on readiness remove every replica from rotation at once. In that topology all traffic, including inference the gateway could still serve, fails at the load balancer until Postgres recovers. The liveness probe on `/healthz` keeps passing, so replicas aren't restarted. Point the readiness probe at `/healthz` instead if you'd rather signed-in developers keep working through a store outage; the cost is that new sign-ins fail against a replica that still reports ready.
193193 
194If your IdP goes down, existing sessions work until `ttl_hours`, and new logins and refreshes fail. Set a longer `ttl_hours` if your IdP has frequent maintenance windows.
194If your IdP goes down, existing sessions work until `ttl_hours`, new logins fail, and a session refresh gets a try-again answer and goes through once the IdP is back. Set a longer `ttl_hours` if your IdP has frequent maintenance windows.
195195 
196196### JWT secret rotation
197197 

zero-data-retention Changed · +1 / -1 lines

from line 52
5252| Feature | Reason |
5353| ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------- |
5454| [Cloud sessions](/docs/en/claude-code-on-the-web), including those started from the [Desktop app](/docs/en/desktop#cloud-sessions) | Requires server-side storage of session data, including conversation history with prompts and completions. |
55| [Claude Tag](/docs/en/claude-tag) | Retains channel memory and session transcripts. |
55| [Claude Tag](https://claude.com/docs/claude-tag) | Retains channel memory and session transcripts. |
5656| [Artifacts](/docs/en/artifacts) | Requires storing published page content on Anthropic-operated infrastructure. |
5757| Feedback submission (`/feedback`, `/bug`, `/share`) | Submitting feedback sends conversation data to Anthropic. |
5858| [Remote Control](/docs/en/remote-control) | Stores the session transcript on Anthropic servers to sync the conversation across devices. |
Feedback