Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Code CLI 26 Oct 2026
One change · claude-code

Claude apps gateway configuration changedclaude-apps-gateway-config

Nearest release: v2.1.311, published an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 26 Oct 2026 21:17 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 26 Oct 2026 21:37 UTC.

Upstream edited
Recorded here
Lines+9added
Lines−0removed
From line 923 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits64to this page, all time

#### Test a policy before deployment

The whole hunk

from line 923, old and new numbered
/
lines
from line 923
923923 
924924When you switch, delete any `serve_to_desktop` line in the same edit that renames the blocks. Where an instruction names the `cli` block, use your `code` block.
925925 
926`serve_to_desktop: true` is a legacy way to offer a policy's `cli` settings to the Code tab. It has no effect when Claude Desktop connects through [`bootstrapUrl`](#claude-desktop-overlay). While your policies use `cli`, a boot warning that names this key means those settings aren't reaching the Code tab:
927 
928* **To cover the Code tab**: switch to `code`, once users' machines meet the conditions in [Apply `code` settings in the Code tab](#apply-code-settings-in-the-code-tab)
929* **To stay on `cli`**: set `serve_to_desktop: false` beside `cli` in a policy to silence the warning
930 
926931#### What goes in `cli`
927932 
928933Each `code` or `cli` value is a complete Claude Code `managed-settings.json` document, the same schema you would deploy via MDM or `/etc/claude-code/managed-settings.json`, expressed here as YAML. The CLI applies the delivered document at the managed tier, above user and project settings, in place of server-managed settings. It therefore ignores the settings [restricted to OS-level policy sources](https://code.claude.com/docs/en/server-managed-settings.md#current-limitations), such as `policyHelper` and `wslInheritsWindowsSettings`.
from line 1003
9981003If a developer declines, Claude Code exits that session rather than applying the policy. When you push a new hook, or any env var that triggers the dialog, to a broad policy, every matching developer therefore sees the dialog in their interactive sessions. A running interactive session shows it on the next hourly poll, and otherwise it appears at the developer's next interactive startup.
9991004 
10001005The `cli` key was named `settings` in earlier releases, and the gateway still accepts that spelling as an alias. For new deployments, use [`code`](#choose-cli-or-code).
1006 
1007#### Test a policy before deployment
1008 
1009To test a policy change, start the gateway against a throwaway Postgres database. The gateway connects to Postgres and applies its schema migrations before it checks the contents of `cli`, `code`, and `desktop` blocks. When it can't reach the database, the start stops at `could not connect to Postgres` and reports nothing about their contents.
10011010 
10021011#### Context window in terminal sessions
10031012 
Feedback