Short description
Doctor checks removed v1 key dreamer.user_memories.enabled instead of v2 task schedule
What happened?
The doctor's section-7 compatibility check (user memories + dreamer) read dreamer.user_memories.enabled, a v1 config key that was migrated to dreamer.tasks["review-user-memories"].schedule in v2. After migrateDreamerV2ForDoctor runs and writes back, the key is gone from the file. The check's default-true logic (userMemObj?.enabled !== false) always fired the warning when dreamer.disable=true, regardless of the actual task schedule. The warning message also told users to set a non-existent setting (dreamer.user_memories.enabled=false).
Diagnostics
$ npx @cortexkit/magic-context@latest doctor
│
● Detected OpenCode — using it for diagnose.
│
◇ Running doctor for OpenCode…
┌ Magic Context Doctor
│
◆ OpenCode installed
│
◆ Magic Context CLI v0.31.3 is current (npm latest v0.31.3)
│
◆ OpenCode config: /home/dev/.config/opencode/opencode.jsonc
│
◆ Magic Context config: /home/dev/.config/cortexkit/magic-context.jsonc
│
◆ magic-context.jsonc parses as valid JSONC
│
◆ Magic Context config loads successfully
│
◆ Plugin registered in opencode.jsonc
│
◆ No conflicts detected (compaction, DCP, OMO hooks)
│
◆ TUI sidebar plugin configured
│
▲ dreamer.user_memories is enabled but dreamer.disable=true, so new promotions will not run. Remove dreamer.disable or set dreamer.user_memories.enabled=false.
│
◆ Embedding provider: local (Xenova/all-MiniLM-L6-v2 bundled)
│
◆ Shared context DB exists at /home/dev/.local/share/cortexkit/magic-context/context.db
│
◆ openDatabase() opened the shared DB
│
◆ SQLite integrity_check: ok
│
● Shared DB row counts: tags=108841, compartments=913, memories=1075, notes=9, dream_runs=19
│
◆ Plugin cache up to date (v0.31.3)
│
● Log file: /tmp/opencode/magic-context/magic-context.log (1722 KB)
│
│ Summary: PASS 14 / WARN 0 / FAIL 0
│
└ Found 1 issue(s) that need manual attention.
Plugin version
latest master
OpenCode version
OpenCode 1.17.15
Platform
Debian Linux
Client
OpenCode CLI
Log output (optional)
$ npx @cortexkit/magic-context@latest doctor
▲ dreamer.user_memories is enabled but dreamer.disable=true, so new promotions will not run. Remove dreamer.disable or set dreamer.user_memories.enabled=false.
Short description
Doctor checks removed v1 key
dreamer.user_memories.enabledinstead of v2 task scheduleWhat happened?
The doctor's section-7 compatibility check (user memories + dreamer) read
dreamer.user_memories.enabled, a v1 config key that was migrated todreamer.tasks["review-user-memories"].schedulein v2. AftermigrateDreamerV2ForDoctorruns and writes back, the key is gone from the file. The check's default-true logic (userMemObj?.enabled !== false) always fired the warning whendreamer.disable=true, regardless of the actual task schedule. The warning message also told users to set a non-existent setting (dreamer.user_memories.enabled=false).Diagnostics
Plugin version
latest master
OpenCode version
OpenCode 1.17.15
Platform
Debian Linux
Client
OpenCode CLI
Log output (optional)
$ npx @cortexkit/magic-context@latest doctor ▲ dreamer.user_memories is enabled but dreamer.disable=true, so new promotions will not run. Remove dreamer.disable or set dreamer.user_memories.enabled=false.