Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Plugin allowed-tools naming CLAUDE_PROJECT_DIR are dropped when there is no folder

In sessions with no project folder, plugin commands and skills lose any allowed-tools entry that names CLAUDE_PROJECT_DIR, and a warning is logged

You'll notice Improvements
JSON All of v2.1.311
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release

Unclear Which kinds of session count as having no folder where tools run is not stated.

What

This extends the same caution about plugin allowed-tools to another case. A plugin command's or skill's allowed-tools field lists tools it may use without asking you. Some sessions have no folder where tools run. In those sessions, Claude Code now drops any allowed-tools entry that names CLAUDE_PROJECT_DIR, the variable that stands for the project folder, and logs a warning. Before, every entry was kept.

Why

If a plugin relies on a tool permission tied to the project folder, that permission will be missing in a session with no folder. The command will then ask before using that tool, or fail to use it.

Read from
Names in the bundleallowed-tools
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich kinds of session count as having no folder where tools run is not stated.

See this entry in the whole of v2.1.311 →

Feedback