{"version":"2.1.282","anchor":"tool-input-echo-setting-is-now-fixed-per-session-and-inherit","canonical_anchor":"tool-input-echo-setting-is-now-fixed-per-session-and-inherit","heading":"Tool-input echo setting is fixed for each session and carried into resumed sessions","tier":"internal","area":"Tool Calls","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/tool-input-echo-setting-is-now-fixed-per-session-and-inherit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Tool-input echo setting is fixed for each session and carried into resumed sessions\n\nWhether tool inputs are repeated back to the API is now decided once per session, and resumed sessions keep that and other prompt-format choices\n\n**Unclear.** When the server sends no value, nothing appears to be saved and echo stays unset, and what that means in practice is unclear.\n\n**What**\n\nClaude Code has a setting, `echoWireToolInputs`, that decides whether the inputs of tool calls (the actions Claude takes, such as reading or editing a file) are repeated back to the API in the conversation history it sends. Before this release it was read fresh on every request, so a remote change could flip it in the middle of a session. Now:\n\n- `echoWireToolInputs` is decided once per session, from the remote setting `tengu_humble_hammock` or the environment variable `CLAUDE_CODE_HUMBLE_HAMMOCK`, and then saved.\n\n- A resumed session inherits the value recorded for it instead of reading the setting again.\n\n- The saved prompt snapshot, a record of how the session's prompt was put together, now also holds `systemTurns`, `toolChangeHeader`, `inlineTools`, `keptReminders`, `echoWireToolInputs` and `contextRendering` (either \"announced\" or \"inline\"). Before, it held only the system prompt, the tool list, `cliPrefix` and `reminderFold`. When a session resumes, these are read back so the conversation keeps its format.\n\n- Claude Code now logs whether a value was recorded, whether it was inherited, where it came from, and when a recorded value is replayed.\n\nSaving the value also depends on a second remote switch, `tengu_foamy_spring`, which falls back to on when the server sends no value; nothing has been read about it yet. For `tengu_humble_hammock`, the previous release built it in as off by default, and the flag server has since returned it as on for this site's account and for an anonymous baseline account; no reading has been taken under this release yet.\n\n**Why**\n\nIn practice, the conversation history Claude Code sends stays in one consistent form for the whole life of a session, including after you resume it, instead of changing shape when a remote setting changes partway through.\n\n- Flag `tengu_humble_hammock`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.282; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Tool Calls\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}