Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Background sign-in warm-up request, blocked under HIPAA policy

Claude Code sends a background /v1/me request to prepare sign-in, and new HIPAA policy entries can deny it and MCP task worker wake-up

Group of 2 You'll notice Improvements
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release

What

Claude Code now sends a small background request to GET /v1/me to prepare its sign-in with the Anthropic API. The request runs quietly without waiting for an answer, retries with a growing delay, and gives up after a timeout. It is skipped unless:

  • the provider is Anthropic's own API (firstParty) and not a gateway, and
  • the policy check allow_api_auth_warm passes.

Two new policy entries are denied for organisations under HIPAA rules when no cached answer is available:

  • allow_api_auth_warm (requirement HIPAA-R59), which controls this warm-up request
  • allow_mcp_task_worker_wake (requirement HIPAA-R57), which controls waking an MCP task worker. MCP is the system that connects Claude Code to outside tools.

Why

The warm-up is a network call Claude Code makes on its own in the background. Organisations under HIPAA rules will not get this warm-up or the MCP task worker wake-up.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhere the worker-restart policy is checked, and so what exactly stops happening, is not confirmed.

See this entry in the whole of v2.1.285 →

Feedback