Sign in
← AI PulseSep 10, 2026

Wire · news · Single-source brief

Claude Code Gateway Updates and Tooling Enhancements

Recent updates to Claude Code include new pricing controls for signed-in clients, enhanced gateway security warnings, and expanded JSON output options for CLI commands.

By Illumora Editorial

Source · Sep 10, 2026, 8:30 PM · On Illumora · Sep 10, 2026, 8:37 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →Claude Code What's New + releases — Claude Code changelog - Claude Code Docs
Save

Recent updates to Claude Code introduce new features for gateway management and developer tooling. These changes aim to provide administrators with more control over access and cost, while offering developers additional command-line interface (CLI) functionality.

Key Points

  • Claude Code clients who are signed in now receive consistent pricing through managed settings, with /cost and telemetry matching the spend meter.
  • A startup warning has been added for gateways when access_control.allow_cidrs is empty.
  • A one-time warning appears when a request first arrives from a public address.
  • The gatewayInternalNetworks managed setting allows administrators to permit /login to a Claude Code gateway from their organization's public IPv4 block.
  • The claude self-hosted-runner --remove-session-state option, which is off by default, deletes each session's per-session directories upon session termination.
  • The configDirectory has been added to the output of claude auth status --json.
  • The --json option is now available for claude plugin install, uninstall, update, enable, and disable commands.
  • errorDetails and noteDetails have been added to each row of claude plugin list --json.
  • Browser-tab icons, chosen by Claude to match each page, are now available for published artifacts.
  • A fix addresses every turn failing with HTTP 400 on third-party Anthropic-compatible endpoints (specifically ANTHROPIC_BASE_URL) since 2.1.265, resolving an issue with a regex in the Artifact tool's input schema.

Context

According to the Claude Code changelog, these updates enhance the platform's administrative capabilities and developer experience. The changes address both security and operational aspects of running Claude Code gateways and using its CLI tools.

Why It Matters

These updates provide administrators with finer control over Claude Code gateway access and cost management, while offering developers more detailed and structured output from CLI commands. This can improve operational transparency and streamline automation for users of Claude Code.

What To Do

  • Review the gateway.yaml settings to understand how pricing is now managed for signed-in Claude Code clients.
  • Note the new startup and public address warnings for gateways to enhance security monitoring.
  • Explore the gatewayInternalNetworks setting if your organization requires /login access from specific public IPv4 blocks.
  • Test the new --json output options for claude plugin commands to integrate them into automated workflows.
  • If using third-party Anthropic-compatible endpoints, verify that the fix for HTTP 400 errors resolves any issues experienced since 2.1.265.

Keep Exploring

/atlas/claude-family /techniques/system-user-separation /studio?pack=foundation