Unclear It is not clear how the earlier version handled a folder named loop.md or other read errors.
What
When you run /loop without a prompt, Claude Code looks for a loop.md file to use instead. It checks the project's .claude/loop.md first, then the loop.md in your user configuration. The way it reads these files has changed:
- a folder named
loop.mdnow counts as no file - both files are trimmed and cut to length in the same way, where before the user one was handled separately
Why
For most people nothing changes. The difference shows only in unusual cases, such as a folder that happens to be called loop.md.
Names in the bundle/loop
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Run prompts on a schedule touched a line naming /loop after this was published.
* When you resume a session with `claude --resume` or `claude --continue`, Claude Code restores the tasks scheduled with `CronCreate`, except recurring tasks that have [expired](#seven-day-expiry) and one-shot tasks whose scheduled time ha…scheduled-tasks see the edit
Confirmed since
Anthropic's documentation has since written up /loop, on Claude Code changelog.
* Fixed `/loop` status updates in self-paced mode often not being shown because Claude wrote them only in its reasoning; Claude now writes each update, and the outcome when the loop stops, as visible textchangelog see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear how the earlier version handled a folder named loop.md or other read errors.
Anthropic's documentation agrees
Anthropic's documentation has since written up /loop, on Claude Code changelog.