Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Claude Code 2.1.329 warns where a folder's hooks live

Written November 20, 2026

Claude Code 2.1.329 adds a trust dialog naming where a folder's hooks are declared, brings scheduled tasks and forks into /tasks, and fixes a settings reset.

Opening a folder someone else prepared in Claude Code has always carried a quiet question: what will run when you start working there? Hooks run commands, so where they are declared matters. The v2.1.329 release notes say this release, published November 19, adds a trust dialog warning that says where a folder's hooks are declared. That turns an invisible detail into something you see before you trust the folder. The same release widens what /tasks shows, adds two diagnostic rows you will actually look for when something fails, and fixes a settings reset that could wipe your own configuration.

The trust dialog names where hooks are declared

The new dialog does one specific thing: it warns and says where a folder's hooks are declared. For a folder you cloned, received from a colleague, or generated with another tool, that location is the starting point for deciding whether to proceed. Instead of hunting through settings files to work out what might run, you get the declaration source named up front, at the moment trust is being asked for.

A second warning covers a different failure. When hooks in managed settings fail to load, a warning now appears in the conversation, in Claude Desktop and in other non-interactive hosts. A managed hook that silently fails to load leaves a gap between what an administrator thinks is enforced and what is actually running. Naming the failure in the surface where the session is happening makes that gap visible rather than leaving it to be discovered later.

/tasks now includes scheduled tasks and forks

/tasks grows from a background-work list into a fuller picture of this session. The release adds this session's scheduled tasks, /loop wakeups, the goal and this conversation's forks to /tasks, with x stopping one after asking. That matters when work is waiting rather than running: a scheduled task or a loop wakeup can surprise you later if you cannot see it now. Bringing those items, the goal, and forks into the same view as other tasks gives you one place to check what this session has set in motion, and the stop action asks first, so cancelling is deliberate rather than a stray keypress.

Diagnostics in /mcp and /status

Two additions put an error message where you are already looking. A server's page in /mcp gains a "Server message" row showing the JSON-RPC error message of a remote HTTP MCP server that refuses the connection. When a server refuses you, that message is often the only explanation the server offers; surfacing it on the server's own page saves a trip through logs. In /status, a new "Marketplace auto-update" row names managed marketplaces that get no automatic updates, and why. If a marketplace is not updating, the row tells you whether that is expected for that marketplace instead of leaving you to guess.

Code Mode can run alongside OpenTelemetry

The release adds support for turning on Code Mode while OpenTelemetry events and metrics are enabled. Each tool call the code makes sends its events; tracing still keeps it off. For teams that rely on OpenTelemetry events and metrics to watch what their sessions do, that removes a choice between using Code Mode and keeping that visibility for ordinary tool calls, while keeping the existing boundary around tracing.

Fixes for a settings reset, code review, and files Claude could not read

The most consequential fix is to your own settings file. The notes say ~/.claude.json was sometimes being reset to defaults when a network stall or file lock made it unreadable and cleared during a save. Losing that file to defaults means losing the configuration you built up, through no action of your own; the fix stops a transient read problem from becoming a permanent reset.

Two other fixes correct work done against the wrong target. /code-review <pr number> sometimes reviewed the checked-out branch instead of the pull request; it now reads the PR with gh pr diff, or says when it can't. And background MCP tasks that stalled after a slow reconnect should stall less often: most HTTP MCP servers now reconnect by themselves when left on an older protocol version. Finally, PDFs, images and Office files sent as application/octet-stream were being saved as .bin so Claude could not read them — that saving behaviour is fixed, so a file that arrives with a generic type can still be read as what it is.

What to do

The previous release in this line is covered in the page linked below.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Claude Code 2.1.328 makes auto mode the cloud default