Workbench Drag Path

Drag files and folders from Obsidian's File Explorer into terminals as usable path text.

Workbench Drag Path makes Obsidian's File Explorer behave better in terminal-heavy workflows. Drag a note, attachment, or folder from the left file tree into a terminal, and the terminal receives a terminal-friendly file system path instead of an Obsidian-internal drag object.

It is designed for people who use Obsidian next to Terminal.app, iTerm2, Termy, Claude Code, Codex, Gemini CLI, shell scripts, and other local tools.

Why

Obsidian is a strong local-first workspace, but file tree dragging is not optimized for terminal workflows. If your vault is also your project notebook, AI context library, or operating console, you often need to pass a note or folder path into a shell command.

Workbench Drag Path keeps that action direct:

drag from File Explorer -> drop into terminal -> path appears

Features

• Drag files or folders from Obsidian's File Explorer as path text.
• Defaults to absolute file system paths.
• Works with Obsidian embedded terminals that accept text drops.
• Works with external terminals that accept text drops, including common macOS terminal apps.
• Copies the same path text to the clipboard as a fallback for terminals that ignore drops.
• Supports shell quoting as an optional setting.
• Supports vault-relative paths as an optional setting.
• Supports multiple selected files or folders.
• Supports space or newline separators for multiple paths.
• Appends a trailing space by default so dropped paths fit naturally into commands.

Usage

1. Open Obsidian on desktop.
2. Open a terminal, such as Terminal.app, iTerm2, Termy, or another embedded terminal.
3. Drag a file or folder from Obsidian's left File Explorer into the terminal input area.
4. The path is inserted as text.

Example output:

/Users/mac/Documents/Obsidian Vault/Projects/My Note.md 

If the terminal does not accept dropped text, paste with Cmd+V / Ctrl+V. The plugin copies the same path text to the clipboard by default.

Settings

Open Settings -> Community plugins -> Workbench Drag Path.

Compatibility

• Obsidian desktop only.
• Tested primarily for desktop terminal workflows.
• The plugin does not run on mobile because it relies on desktop drag-and-drop behavior.

Terminal drop behavior is controlled partly by the receiving terminal application. Most terminals that accept text drops should work. If a terminal ignores dropped text, use the clipboard fallback.

Privacy

Workbench Drag Path runs locally inside Obsidian.

• No telemetry.
• No network requests.
• No external services.
• No file contents are read.
• Only dragged file or folder paths are written to the drag payload and, if enabled, the clipboard.

Limitations

• External terminal support depends on whether the terminal accepts text/plain drop data.
• Obsidian's File Explorer DOM can change between app versions. If dragging stops working after an Obsidian update, please open an issue.
• The plugin does not create terminal sessions. Pair it with your preferred terminal plugin or terminal app.

Installation

From Obsidian Community Plugins

After approval:

1. Open Settings -> Community plugins.
2. Turn off Restricted mode if needed.
3. Click Browse.
4. Search for Workbench Drag Path.
5. Install and enable the plugin.

Manual install

1. Download the latest release from GitHub Releases.
2. Copy manifest.json, main.js, and styles.css into:

<your-vault>/.obsidian/plugins/workbench-drag-path/

3. Reload Obsidian.
4. Enable Workbench Drag Path in Settings -> Community plugins.

Development

npm install
npm run build

Build output:

• main.js
• manifest.json
• styles.css

For local testing, copy those files into a vault plugin folder:

<your-vault>/.obsidian/plugins/workbench-drag-path/

Release Checklist

Before submitting to the Obsidian community plugin directory:

• Confirm manifest.json has the correct id, name, version, minAppVersion, and isDesktopOnly.
• Update versions.json.
• Create a GitHub release tag that matches manifest.json, such as 0.1.0.
• Attach manifest.json, main.js, and styles.css to the release.
• Make the repository public.
• Submit the plugin to obsidianmd/obsidian-releases.

License

MIT