Claude Code v2.1.223 ·
Workflow save and discovery can run through the storage backend
Your saved workflows can be listed and stored through a storage backend rather than plain files.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
In DevelopmentKind: in v2.1.223,
In DevelopmentSection of the release
What
User workflows can be enumerated and saved via storage keys instead of directory scans and file writes.
Details
- discovery pages through
listEntries, counting near-miss extensions, oversize files and unreadable files - saving uses
mode: 384 and adds an ifAbsent precondition when not overwriting; an AlreadyExists result raises the existing name-collision error - cache invalidation and
tengu_workflow_saved telemetry after a save were factored into a shared helper used by both the file and backend paths
Evidence
could not be read through the storage backend
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.223 →
