Tool-input echo setting is fixed for each session and carried into resumed sessions

What

Claude 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:

• echoWireToolInputs is decided once per session, from the remote setting tengu_humble_hammock or the environment variable CLAUDE_CODE_HUMBLE_HAMMOCK, and then saved.
• A resumed session inherits the value recorded for it instead of reading the setting again.
• 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.
• Claude Code now logs whether a value was recorded, whether it was inherited, where it came from, and when a recorded value is replayed.

Saving 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.

Why

In 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.