dsh-skills-mcp-panel

LIMITATIONS

Known limitations

- **A panel change is not a preset edit.** A skill or MCP row that a preset's `agent.cordis.yml` provides is still composed at session creation; the panel's MCP selections target the profile patch layer, which applies to every session. Hiding a whole preset-provided row remains a preset edit, and a new session is what picks it up. - **Startup-frozen profiles.** `headless`, `sdk`, and `acp` default to `patchReload: startup`; the panel's MCP writes land there but apply at the next launch, and the page says so right after such a change. Skills stay hot everywhere, because the skill provider watches files rather than configuration. - **Skills are read from disk, not from the registry.** The panel mirrors the filesystem provider's discovery (top-level `SKILL.md` bundles and flat `<name>.md` files, dot-directories skipped) so it can rewrite the file that actually controls visibility. A skill supplied by a different provider appears in the model's catalog but has no file for this panel to change. - **No import, create, or delete.** The page changes what already exists; it never adds or removes a skill or a server. - **MCP has no project-level source.** DSH composes MCP servers from the profile, the harness home, and bundles — there is no per-project MCP file to read — so a server lands in a project group only when its own `cwd` points into that project. Everything else is Global, which is the truth rather than a gap.