Unclear Which development-folder sources this applies to, and whether function hooks themselves are switched off by default, are not settled.
What
Some plugins ship a function-hook module ("mods"): code that runs at points in Claude Code's work. When such a plugin loads from a development folder, Claude Code now lays out a "type root" in the plugin's folder, which gives code editors the type information they need to check the code.
- A
typesdirectory with a.gitignorecontaining*, so git ignores it. index.d.tsdeclaration files for the mod and its dependencies, linked or copied in, including one forclaude-codestamped with the running CLI version.- A
tsconfig.jsonin the types directory, and one at the plugin root unless the plugin has ajsconfig.json. - Each result is logged as "type root of … at …". If the path would lead outside the mod's folder, the type root is not laid and that is logged.
- The plugin file watcher now ignores the types directory, so writing these files does not trigger a plugin reload.
Why
Plugin authors writing function hooks can get editor type-checking against the Claude Code version they are running without setting anything up. New files now appear in the plugin folder, which is worth knowing if you keep that folder under version control.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which development-folder sources this applies to, and whether function hooks themselves are switched off by default, are not settled.