dsh-inherit

When you juggle several AI coding tools, your MCP servers and Skill definitions live in scattered config directories — ~/.claude, ~/.cursor, ~/.codex, ~/.cc-switch — and DSH previously offered no first-class way to pull them in. dsh-inherit adds a single row under Settings → General that opens a centered modal, auto-scans every source on your machine, and lets you toggle which agents and categories to bring over. A mandatory dry-run preview lists exactly what would be imported, skipped, or annotated before you confirm a write, and every target file receives a .bak backup before modification.\n\nUnder the hood, MCP servers are composed into cordis.patch.yml as @deepseek-ai/dsh-mcp-client rows, working with no manager plugin, Hanihahaha-style UIs, and future official UIs alike; the auto-detected alternative target ~/.dsh/mcp.json is also supported. Skills are copied as SKILL.md directories into ~/.dsh/skills with idempotency — same-name entries are simply skipped. For items DSH reads natively (CLAUDE.md, AGENTS.md) or that capability-matched community plugins already handle (memory, model routing), the plugin detects and annotates them via capability matching rather than hard-coded plugin names, so forks and differently-named plugins are recognized correctly. cc-switch's SQLite database (providers, prompts, MCP, Skills) is currently the only source this plugin reads from that no other community mover covers.\n\nIt is built for DSH users who have accumulated MCP configurations and Skill definitions across Claude Code, Cursor, Codex CLI, or cc-switch and want a structured, reversible way to migrate them in one pass. It does not yet move hooks, slash commands, or session history — pair it with dsh-claude-move or dsh-chat-import for those. Keep in mind that MCP credentials are written in plaintext to the target file, variable references are not yet converted, and rollback is manual via the .bak files, so review your sources and file permissions accordingly.