Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Code Mode is an experimental opt-in tool-calling feature. Its linked setup and organization-disable guide returned HTTP 404 when checked on November 13, 2026, so the steps and general availability could not be verified.
- Organization settings and policy requests no longer use a proxy supplied only through ALL_PROXY. If those requests need a proxy, set HTTPS_PROXY according to approved organization policy.
- The engines["claude-code"] range in plugin.json affects whether a plugin is installed, updated, or loaded; install and update select the newest compatible plugin version.
- claude plugin validate type-checks a plugin’s TypeScript hooks module. Findings are warnings by default and make the validation command fail when --strict is used.
Code Mode is experimental; setup steps remain unverified
The Claude Code 2.1.323 changelog is dated November 12, 2026. It adds Code Mode, an experimental, opt-in feature in which Claude writes JavaScript to call its available tools.
The release links to an official guide for enabling Code Mode and turning it off for an organization. That exact page returned HTTP 404 when checked on November 13, so personal setup steps, organization-disable steps, account eligibility, regions, and prices remain unverified.
This observation does not establish availability across all accounts or the status of the service as a whole. The changelog also provides no measured speed, token-use, or cost benefit; whether Code Mode replaces Manual or Auto permission modes remains unverified.
The ALL_PROXY change is limited to organization requests
The proxy change in 2.1.323 has a narrow scope: organization settings and policy requests no longer use a proxy configured only through ALL_PROXY. The release note says to set HTTPS_PROXY if those requests need a proxy on your network. It names organization settings and policy requests; it does not describe a universal change to all Claude Code traffic. Do not infer that every other request ignores ALL_PROXY or must use HTTPS_PROXY.
When troubleshooting, first identify whether the failing request is an organization settings or policy request, then check where that runtime actually reads proxy settings. If one of those requests fails and the environment supplies only ALL_PROXY, ask the administrator to review HTTPS_PROXY under the approved network policy. Do not extend this change to model API calls, tool calls, or all desktop traffic. ANTHROPIC_BASE_URL for an API gateway is a separate routing setting, not another name for a proxy variable.
Plugin version ranges affect installation, updates, and loading
This release adds an engines["claude-code"] version-range gate to plugin.json. A plugin outside its declared Claude Code version range is not installed, updated, or loaded. An install or update selects the newest plugin version that fits the range. If a plugin is missing or does not load, check both the Claude Code version in the affected runtime and the range declared by that plugin; the newest version shown in a marketplace is not necessarily compatible.
Check the runtime, validator, and proxy settings source
Run claude --version in the command-line entrypoint where the problem occurs, and note whether you launched from a terminal, editor, or desktop session. If the issue is in a desktop or other host-managed session, separately confirm that the host has incorporated 2.1.323; a CLI version does not prove that an embedded session runs the same build. Plugin maintainers can run claude plugin validate to see TypeScript hook-module findings. They appear as warnings by default; with --strict, findings make the validation command fail.
Record when the error occurred, the failing request category, the settings source used by that runtime, and the original error text with secrets removed. The official network guide says shell-exported variables are read at startup, so a changed shell setting applies to a newly launched session. For Claude Desktop sessions where the app manages the provider connection, proxy settings are read from managed settings and ~/.claude/settings.json. Check the approved configuration for the actual entrypoint, and do not disable TLS verification to hide a certificate or proxy error. The guide also explicitly states that Claude Code does not support SOCKS proxies; a SOCKS address is not a directly usable HTTPS_PROXY configuration.
Sources
Frequently Asked Questions
Should every plugin set 2.1.323 as its minimum Claude Code version?
No. Set engines["claude-code"] to the range the plugin actually supports. The range affects install, update, and load eligibility, but the changelog does not prescribe a common range for all plugins.
Does a failure from claude plugin validate --strict prove that a plugin cannot load?
Not by itself. In 2.1.323, --strict makes TypeScript hook-check findings fail the validation command. The same changelog separately describes the version-range gate for plugin installation, updates, and loading; it does not equate the two outcomes. Track the CI validation result separately from runtime compatibility.