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:
/dream should 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": true in ~/.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.
Description
AutoDream toggle shows in
/memoryinteractive menu,autoDreamEnabledistruein~/.claude/settings.json, but/dreamreturns "Unknown skill: dream" and no background dreaming task starts.Steps to Reproduce
/memory— interactive menu appears with "AutoDream: On" and "use /dream to run"/dream— returns "Unknown skill: dream"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)Environment
"autoDreamEnabled": truein~/.claude/settings.jsonAdditional Context
The
/memorymenu 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/dreamcommand 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.