AutoDream: /dream returns 'Unknown skill' and no background task starts despite toggle being ON
Open 💬 17 comments Opened Mar 24, 2026 by JFord925
Description
AutoDream toggle shows in /memory interactive menu, autoDreamEnabled is true in ~/.claude/settings.json, but /dream returns "Unknown skill: dream" and no background dreaming task starts.
Steps to Reproduce
- Open Claude Code v2.1.81 (latest on npm as of 2026-03-24)
- Run
/memory— interactive menu appears with "AutoDream: On" and "use /dream to run" - Type
/dream— returns "Unknown skill: dream" - Type "run your autodream" in natural language — Claude responds that it doesn't have that skill
- Check task list — no background "dreaming" task was spawned
- Status bar shows no dreaming activity
Expected Behavior
Based on the Nate Herk video showing AutoDream working:
/dreamshould trigger a background dreaming task (even if it returns "Unknown skill" in the chat)- Status bar should show "dreaming"
- Task list should show a dream consolidation task reviewing sessions and updating memory files
Environment
- Claude Code version: 2.1.81
- Platform: Windows 11 Pro 10.0.26200
- Shell: Git Bash
- Settings:
"autoDreamEnabled": truein~/.claude/settings.json - Auto memory: Enabled, with active memory files in project memory directory
- Plan: Max (Opus 4.6 with 1M context)
Additional Context
The /memory menu correctly shows the AutoDream toggle as ON and displays "use /dream to run" — so the UI layer recognizes the feature. The disconnect is that the /dream command handler and background task spawner don't appear to be wired up in this build. The setting exists, the UI exists, but the execution path is missing.
17 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Seeing the video I immediately tried myself.
/memoryconfirmslast ran 1d agoTrying
/dreamorrun auto-dreamtoday reproduces the same findings as reported above.I was hoping the update I installed today fixed this really stupid bug, but it did not.
Same issue. Doesn't work on v2.1.84 (last run 1 day ago). But today I updated Claude CLI to v2.1.85 and now dream works automatically after every larger prompt (couldn't figure out the underlying logic). Typing /dream reproduces the same findings as mentioned above.
This is still an issue in v2.1.85
same here
This is still an issue in v2.1.86
I built this as a plugin you can install now while waiting for the official rollout.
Install:
Then run:
It audits your memory files, flags format violations/stale content/duplicates, proposes changes, and only executes after your approval.
Repo: https://github.com/jl-cmd/claude-dream
this still is an issue in 2.1.87
still an issue in 2.1.89
still an issue in 2.1.91
still an issue in 2.1.92, so what‘s the time to fix?
I genuinely don't think anthropic looks at issues
just fork the code and fix it yourself at this point 😂 we might die waiting
On Tue, Apr 7, 2026 at 9:36 AM Scott Willsey @.***>
wrote:
Also experiencing this.
autoDreamEnabled: trueis set in settings.json, but the toggle has disappeared from the/memorysubmenu and/dreamdoes not register as a command. Claude Code on macOS, latest version.Still in issue in 2.1.107.....
Honestly, quite amusing. It's not like a secret skill, they prompt you themselves to launch /dream command. And it's not working for almost a month now..
same for v2.1.116