Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.236 Home All releases ←olderv2.1.235 v2.1.237newer→
Claude Code v2.1.236

Kill switch for Harbor request pacing

Use it now
Useful3 Signal3
Internals Notable not in their notes

You can switch off Harbor request pacing with a new environment variable.

Feature flag
tengu_harbor_kite_pacing_off Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.236: on

Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you

CLAUDE_CODE_HARBOR_KITE_PACING_OFF
What

Pacing of Harbor requests now has an explicit off switch instead of a per-turn latch. Set CLAUDE_CODE_HARBOR_KITE_PACING_OFF to turn pacing off, or it can be turned off remotely by the tengu_harbor_kite_pacing_off flag.

Details
  • The flag falls back to false, and the flag means "off", so pacing is on by default in this build unless the environment variable or remote config disables it.
Evidence

tengu_harbor_kite_pacing_off

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.236 →