Using the workspace

Bring your setup

Bring the skills, instructions, MCP servers and allowed commands you already have in other coding tools into Duscode. You read each one before anything changes, and nothing you have is overwritten.

If you already use other coding tools, you have probably written skills, instructions and server settings for them. Duscode can find them on this computer and bring the ones you choose over, so you start with your own setup.

Open it from the first-run prompt in a new session, from Settings → Memory & skills → Bring your setup, or from Apps & connectors when it found MCP servers.

What it looks for

Each item says what it is, where it was found and whether it applies to all projects or this one. Some need nothing: a project's CLAUDE.md, AGENTS.md and .cursor/rules are already read where they are, so they are listed as used where they are.

Choose, read, approve

1. Choose. Tick what you want. Everything new is ticked at first.
2. Read. Review shows exactly what will come over: the skill's text, the instructions, what a server runs, or the commands. Anything that reads like an instruction to an agent, a secret written into a file, or a very broad command rule is pointed out.
3. Approve. Nothing changes until you approve. If an item changes in its tool between your review and your approval, it isn't brought over: review it again.

Copy or keep in sync

Skills can come over as a copy (today's version) or kept in sync (Duscode reads the original folder). A skill kept in sync is trusted only while it is what you approved: if it changes in its tool, Dus stops using it and the dialog shows it as changed, waiting for your review.

Names that are taken

If you already have a skill or MCP server with the same name, or Duscode has a built-in skill by that name, the item is shown as a conflict with a suggested new name. Pick a name or leave it unticked. Duscode never overwrites what you have.

Where things go