A failed plugin hook prefetch at startup is now logged instead of blowing up.
What's wrong with this entry?
Startup awaits an extra hooks-snapshot step when a storage handle is present, both at launch and after entering a worktree, and a failure to prefetch plugin hooks is now caught and logged instead of surfacing as an unhandled error.
- The snapshot branch requires both a non-undefined storage handle and a further condition that is not resolved in this build.
- The
bridgefast path now primes fast-path credentials and seeds install IDs before the policy check.
plugin hooks prefetch:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Startup prefetch failures no longer surface
Both mention startup
-
v2.1.239
Deleted working directories are detected at startup and handled during hooks
Both mention startup
-
v2.1.242
A socket path taken by another running Claude Code no longer breaks startup
Both mention startup