dsh-plugin-dreaming

LIMITATIONS

Known limitations

- **No edits by default**: `dream.autoApply` is `false`, so dreams journal proposals without touching files. Enable it explicitly to correct descriptions/boundaries (backups, journal, conflict detection and revert still apply). - **Suggestions need samples**: the first calls of a new skill show only low-confidence hints; the plugin deliberately never fabricates a high score without evidence. - **Non-editable sources**: bundled / project / runtime skills can only improve through the injected guidance overlay; their files are never rewritten. - **Capability edits are heuristic**: dream proposals pass deterministic validation, but a “better description” can still introduce bias; that is why backups, journal, conflict detection and single-step revert exist. - **Dream is inline-only in v1**: the night usually has no live parent agent; `dream.mode` is recorded truthfully as `inline` and logs one warning. - **Symlinks are not edited**: if a skill's `SKILL.md` is a symlink the plugin refuses to write (`symlink-path`) and only records a suggestion, so the link is never replaced by a regular file. - **Local trust boundary**: `/dreaming/api/` has no extra auth beyond the loopback binding (POST has an Origin check). Do not expose the profile's listener on a non-loopback address without adding authentication, and treat the data directory and backups as local user data. - **`POST /dreaming/api/dream/run` runId**: the run is asynchronous; the call returns `accepted:true` immediately and `runId` may be `null` — the actual run id is in the next journal refresh. - **Judge quality depends on the model**: scores are relative signals for trends and prioritization, not absolute truth. - **Sub-agent probe**: `probe.mode = 'subagent'` creates a real sub-session, costs significantly more and is subject to delegation depth/capacity; failures fall back to inline.