Dune runs VS Code extensions from Open VSX in a real extension host, lets you switch its own built-in features on and off, and lets you shape the agent with plain files in your repo.
Extensions run in a separate host process, on Node or Bun, against the VS Code API. Commands, views, webviews, tree views, terminals, decorations, the language provider APIs, debugging, SCM, tasks and tests are covered, and an API conformance suite tracks the gaps.
- Install from Open VSX in the Extensions view or with dune --install-extension
- Drop a .vsix into ~/.dune/extensions, or reuse ~/.vscode/extensions
- Microsoft-only extensions (Pylance, Copilot, C/C++) can't be installed; open alternatives can
Dune's own features ship as internal extensions. Non-core ones, the terminal among them, can be disabled, and a lean workbench boots lean.
Rules, a constitution, skills, slash commands, modes, subagents, hooks and MCP servers are plain files in .dune/ for the project, or ~/.dune for you. Check them in and the whole team's agent behaves the same way.
More on the agent| Namespace | Coverage |
|---|---|
| commands | Register, execute, and contribute to menus and keybindings |
| window | Messages, quick input, output, status bar, decorations, tabs, views, webviews, trees, terminals |
| workspace | Documents, configuration, file system, search, file watching |
| languages | Diagnostics and the language provider matrix |
| debug · scm · tasks | Debug sessions, source control providers, task running |
| env · extensions | Environment, extension lookup, ExtensionContext |
A warm, AI-first workbench. Free to download. Bring your extensions, your themes, and your agent.