Obsidian Plugin Retirement

The DorkOS plugin for Obsidian is retired. New versions no longer include or maintain it. We are focusing on the web, desktop, phone, Cloud and spaces.

Your vault is still a folder of Markdown files. You can work with that folder in the normal DorkOS app. This does not restore the plugin's in-vault features.

What changes

The retirement removes the DorkOS sidebar inside Obsidian. It also removes automatic active-note context, dragged-in note context, and opening notes in Obsidian from chat.

The normal app does not know which note you are reading. Tell your agent which files to use. You can keep Obsidian open alongside DorkOS to read or edit your notes.

The retirement does not delete your notes or chat history. DorkOS does not uninstall an old plugin from your vault automatically.

Work with a vault in the normal app

1. Install DorkOS and open the app.
2. Choose your vault folder as the agent's working folder.
3. Tell the agent which notes to read and what you want it to do.

DorkOS and the agent need permission to access that folder. Your configured folder boundary and normal approval settings still apply. A vault on another device must be available to the computer running the DorkOS server; opening the phone app alone does not transfer it.

The old plugin used the vault's parent folder as its working folder. To find its earlier Claude Code chats, check that parent folder in DorkOS under the same local account. This is a place to look, not a promise that every old chat will appear. Keep your existing agent history while checking.

Remove an old plugin install

1. In Obsidian, open Settings > Community plugins and disable DorkOS Copilot.
2. Use Uninstall if available. For a manual install, remove only <vault>/.obsidian/plugins/dorkos-copilot/.
3. If that path is a symbolic link, remove the link itself, not the source folder it points to.

Keep your vault, your DorkOS data folder, and your agent's chat history. The plugin used DORK_HOME when set, otherwise ~/.dork, and Claude Code's own transcript storage. Its data was not confined to the plugin folder. There is no need to erase any of these folders to retire the plugin.

Historical source and recovery

This section is for developers who need to inspect or recover the old source. It does not describe a supported installation.

The preserved pre-removal source snapshot is:

• Commit: dbff5a6f6b3005d4e9815d1b3d485446528f2900
• Repository tree: 63cb22d2e6011aa358b406be3bc83491323662c6
• Plugin source: apps/obsidian-plugin/ at that commit

Recover it in a separate checkout so the current app stays untouched:

git clone https://github.com/dork-labs/dorkos.git dorkos-obsidian-history
cd dorkos-obsidian-history
git switch --detach dbff5a6f6b3005d4e9815d1b3d485446528f2900
git rev-parse HEAD^{tree}

The last command should print the tree above. The historical checkout includes the old build instructions and lockfile. Historical builds may need dependencies or native binaries that are no longer available. The plugin was under-tested before retirement; preserving its source does not verify it on current Obsidian versions. No new plugin binary is published for this retirement.

Why retire it?

The plugin needed a separate execution path, build fixes, native database packaging, and Obsidian theme handling. Those costs continued without proving the complete experience inside Obsidian.

Public source-build instructions existed, so people may have installed it themselves. We do not know how many did. Keeping this page at its old address gives those users migration and recovery guidance.

A future Obsidian client could connect to the normal DorkOS server if real demand appears. That is a possible direction, not a planned release or a replacement included here.