tengu_humble_hammock

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.257, including the newest one read.

Releases whose published page names tengu_humble_hammock.

1. v2.1.282 24 Sep 2026
   Whether tool inputs are echoed to the API is now fixed for the whole session

   The choice to echo tool inputs back to the API is now made once per session and kept when you resume, instead of rechecked every call

   gate cited by this entry

2. v2.1.282 24 Sep 2026
   Claude Code can record the API requests it sends into session transcripts

   New, off-by-default recording writes each API request's system prompt, tools and message changes into the session transcript file

   gate cited by this entry

3. v2.1.282 24 Sep 2026
   Resumed sessions keep more of the prompt format they started with

   Resuming a session now restores more saved choices about how the prompt was laid out, instead of picking them again

   gate cited by this entry

4. v2.1.281 23 Sep 2026
   CLAUDE_CODE_TETHER_LIVE=true now opts in to several related threads/tether features and bypasses first-party checks

   CLAUDE_CODE_TETHER_LIVE=true now also turns on related threads features and skips some endpoint checks

   gate cited by this entry, found in this entry's text

5. v2.1.281 23 Sep 2026
   Dark-launched attachment hooks (tengu_humble_hammock, build-time-false branch)

   The humble hammock switch now also decides whether copies of tool input are placed into messages when attachments are built

   gate cited by this entry, found in this entry's text

6. v2.1.281 23 Sep 2026
   Stellar-drift and humble-hammock features forced on when the CLAUDE_CODE_TETHER_LIVE opt-in holds

   CLAUDE_CODE_TETHER_LIVE can now force the stellar-drift and humble-hammock features on for first-party use

   gate cited by this entry, found in this entry's text

7. v2.1.281 23 Sep 2026
   toolInputCopies recorded in declared-tools state behind tengu_humble_hammock

   Declared-tool entries can carry a toolInputCopies list, applied only when tengu_humble_hammock or CLAUDE_CODE_HUMBLE_HAMMOCK is on

   gate cited by this entry, found in this entry's text

8. v2.1.257 1 Sep 2026
   Wire-format echo debugging fields (tool inputs + block order) are built but flag-gated off

   Two transcript debugging aids, raw tool inputs and exact wire block order, are computed but each sits behind its own gate.

   gate cited by this entry

9. v2.1.257 1 Sep 2026
   Renamed/relaunched print-engine-loop flag as 'humble hammock'

   The env var controlling print and engine loop behavior was renamed to CLAUDE_CODE_HUMBLE_HAMMOCK and still defaults to off.

   found in this entry's text, gate cited by this entry

Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.

One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.

The earliest release whose published evidence quoted tengu_humble_hammock was v2.1.281, 23 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.