dsh-memoryos

LIMITATIONS

已知限制

- Process-wide enablement means concurrent enabled and disabled Agents should use separate DSH launches. - The switch controls subsequent requests. Memory already copied into the current chat transcript cannot be retracted; start a new Session when a fully clean context is required. - The default state path is shared by local launches. Set a distinct `MEMORYOS_STATE_FILE` for profiles that need independent switch state. - The plugin is intentionally coupled to RC5 Cordis lifecycle and event surfaces. - Profiles without `headless-runner` can emit a non-fatal missing-entry warning for the optional resume overlay during `--dump-config`; memory tools, usage collection, and Loader/HMR composition still pass. The overlay is only needed for controlled continuation benchmarks. - The controlled history-eviction hook is evaluation-only. - Memory guidance remains evidence, not authority; verify code-related facts in the checkout and run tests. See [SECURITY.md](SECURITY.md), [CONTRIBUTING.md](CONTRIBUTING.md), and the [MIT license](LICENSE).