Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

Workflow save and discovery can run through the storage backend

Under the hood
Useful2 Signal0
Elsewhere

Your saved workflows can be listed and stored through a storage backend rather than plain files.

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 →