A bad skill or command directory no longer produces a startup error; workflows are pre-warmed too.
tengu_workflows_enabled Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.234: off
Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The startup prefetch now calls a dedicated cache warmer instead of building the full command list. Skill and command loads run together and every failure is swallowed, so a bad skill or command directory no longer produces a startup error. The warmer also pre-loads workflows.
- The loads run under a settle-all wrapper inside a try/catch, and the skills load time is still recorded as a startup phase.
- Workflow warming short-circuits when workflows are off: the
enableWorkflowssetting set to false, theCLAUDE_CODE_WORKFLOWSenvironment variable set to false, or thetengu_workflows_enabledgate (fallback true) off.
warmCommandSourceCaches
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.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
-
v2.1.246
Startup banner summarising what changed since you last read the release notes
Both mention startup