Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

Insights requests opt into sendSideQueryBeta

The /insights model request, including its facet extraction, now sets sendSideQueryBeta, and the insights run uses a new running-flag mechanism

Group of 2 Under the hood Internal Changes
JSON All of v2.1.318
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
InsightsArea: what it touches
Internal ChangesKind: in v2.1.318,
Internal ChangesSection of the release

What

The request that /insights sends to the model now sets sendSideQueryBeta: true, alongside querySource: "insights". A side query is a separate, smaller model request made in the background, apart from the main conversation.

  • The insights facet extraction side query sets sendSideQueryBeta.
  • Another part of the code treats a request as eligible for some beta handling when its querySource is in a fixed list or when sendSideQueryBeta is true. Insights requests now meet that condition. The members did not trace what that handling is.
  • Other call sites set the same option.
  • The insights run now uses a new mechanism that tracks whether it is currently running.

Why

In practice, /insights requests may now be sent differently, for example with a beta header or along a different request path. A beta header is an extra label on a request that switches on features still being tested. If insights results or failures change after this release, this is a likely place to look.

See this entry in the whole of v2.1.318 →

Feedback