Workspace++
approvedby s1m4ne
Workspace session manager with a native-feeling UI/UX. - This plugin has not been manually reviewed by Obsidian staff.
Workspace++
Workspace++ is an Obsidian community plugin for saving, switching, and organizing workspace sessions. It is built for people who want Obsidian layouts to feel fast, native, and keyboard-friendly.

Highlights
- Save the current workspace layout as a named session.
- Switch sessions from the status bar, quick switcher, command palette, hotkeys, or session manager.
- Use automatic save-on-switch, or turn it off for a manual save workflow.
- Organize sessions into groups.
- Customize status bar click, middle-click, right-click, and modified-click actions.
- Scroll on the status bar to switch sessions.
- See a status bar warning when a manual-save session has unsaved layout changes.
- Save, reload, duplicate, rename, delete, reorder, and bulk-delete sessions.
- Keep per-session version history and restore previous layouts.
- Export, import, and restore session backups.
- Load sessions from note frontmatter with
workspace-session. - Save the current note name as a session and write the matching frontmatter automatically.
- Use Workspace++ in 21 interface locales.
Features
Quick switching
Cycle through sessions with Cmd/Ctrl+Shift+Enter, or move backward/forward with Cmd/Ctrl+Shift+, and Cmd/Ctrl+Shift+.. You can also register numbered or name-based session switch commands for custom hotkeys.

Session manager
Open the session manager to switch, create, rename, duplicate, delete, reorder, bulk-delete, and group sessions.

Create, duplicate, delete
Create sessions from the current layout, duplicate the active session with Cmd/Ctrl+Shift+M, or delete it with Cmd/Ctrl+Shift+Backspace.
Rename and reorder
Rename the current session with Cmd/Ctrl+Shift+R, right-click sessions for context actions, and drag sessions to reorder them.
Status bar workflow
The status bar shows the active group and session. By default, click opens the quick switcher, Cmd/Ctrl+Click saves the current session, right-click opens the session menu, and Cmd/Ctrl+Right-click restores the latest version history entry.
You can customize status bar click actions in settings, including save, save as, reload without saving, rename, duplicate, previous/next session, blank session, version history, and "save current note name as session".
Save modes
Workspace++ defaults to automatic save-on-switch. If you prefer a manual workflow, turn auto-save off and use explicit save/reload commands. In manual mode, Workspace++ can warn before switching away from unsaved layout changes and highlight the status bar when the current layout differs from the saved session.
Manual-save tools include:
- Save current session.
- Save current session as a new session.
- Save the current layout to another existing session.
- Reload the current session without saving local layout changes.
Session groups
Groups let you organize sessions without deleting or duplicating them. You can switch groups, show all sessions, move sessions between groups, remove sessions from groups, and disable the group feature if you do not need it.
Version history and backups
Workspace++ keeps per-session version history for layout changes and can restore previous layouts. It also keeps session backup files in the vault and supports manual export/import snapshots from settings or commands.
Automatic rotation backups are created on save, hourly, up to 3 generations.
Frontmatter sessions
Add this property to a note to load a session when that note is opened:
workspace-session: My Session
Workspace++ also provides a command, Save current note name as session, that writes workspace-session: <note-name> to the current Markdown note and creates or overwrites the matching session using the current layout.
Local settings
Workspace++ can keep settings local to the current vault, while session data remains in the vault-level Workspace++ storage folder. This is useful when syncing .obsidian settings across vaults but keeping Workspace++ behavior different per vault.
Installation
From Community Plugins
- Open Obsidian Settings > Community plugins.
- Click Browse and search for Workspace++.
- Click Install, then Enable.
Community plugin page:
https://community.obsidian.md/plugins/workspace-plus-plus
From release
- Download
main.js,manifest.json, andstyles.cssfrom the latest release. - Create a folder at
<your-vault>/.obsidian/plugins/workspace-plus-plus/. - Place the three files into that folder.
- Open Obsidian Settings > Community plugins and enable Workspace++.
With BRAT
Use BRAT if you want to test unreleased changes directly from GitHub.
- Install the BRAT plugin.
- Open Settings > BRAT > Add Beta plugin.
- Paste this URL and click Add Plugin:
https://github.com/s1m4ne/obsidian-workspace-plus
Commands
All commands can be assigned custom hotkeys in Settings > Hotkeys.
| Command | Default hotkey |
|---|---|
| Manage sessions | - |
| Create new session | - |
| Create blank session | - |
| Duplicate current session | Cmd/Ctrl+Shift+M |
| Rename current session | Cmd/Ctrl+Shift+R |
| Delete current session | Cmd/Ctrl+Shift+Backspace |
| Previous session | Cmd/Ctrl+Shift+, |
| Next session | Cmd/Ctrl+Shift+Enter, Cmd/Ctrl+Shift+. |
| Switch to session 1-9 | Assignable |
| Save current session | Cmd/Ctrl+Shift+S |
| Save current session as... | - |
| Save current note name as session | - |
| Save current layout to session... | - |
| Reload current session without saving | - |
| Toggle auto-save on switch | - |
| Enable auto-save on switch | - |
| Disable auto-save on switch | - |
| Search sessions | - |
| View session version history | - |
| Export sessions snapshot | - |
| Import latest sessions snapshot | - |
| Switch group | - |
| Show all sessions / exit group | - |
| Next group | Cmd/Ctrl+Shift+Tab |
| Previous group | - |
Sync and storage
Workspace++ stores session data in the Obsidian plugin folder for new installs:
.obsidian/plugins/workspace-plus-plus/sessions.json
Existing installs that already use the older vault-local folder keep using it automatically:
.workspace-plus-plus/sessions.json
You can move session storage in Settings > Workspace++ > Advanced. Use the Obsidian plugin folder if you want Obsidian Sync to sync Workspace++ sessions across devices. Use the vault-local .workspace-plus-plus folder if you share .obsidian across multiple vaults with tools such as Settings Profiles and want each vault to keep separate sessions.
Immediate backups and rotation backups are stored next to the active session file:
sessions.backup.json
backups/
Workspace++ watches the active session file for external changes and reloads synced updates when possible, but concurrent edits are not a full conflict-free merge system. If you use Syncthing, Dropbox, iCloud, Obsidian Sync, or another file sync tool, let sync finish before editing sessions on another device. Automatic backups help recover from corrupted session data, but they are not a full multi-device conflict resolver.
Languages
Workspace++ includes 21 interface locales:
English, Arabic, Bengali, Chinese Simplified, Chinese Traditional, French, German, Hindi, Indonesian, Italian, Japanese, Korean, Malay, Persian, Polish, Portuguese, Russian, Spanish, Thai, Turkish, and Vietnamese.
Video Demos
Show video demos
Quick switching
https://github.com/user-attachments/assets/b1dc94f7-b979-4b09-97e6-3ebf4837b5ed
Session manager
https://github.com/user-attachments/assets/27a02a7b-aaa8-4795-b67d-4348fa4012f7
Create, duplicate, delete
https://github.com/user-attachments/assets/c86b8000-c49e-442c-8246-17c181a4d921
Rename and reorder
https://github.com/user-attachments/assets/6041d80f-9c15-4a59-8d27-8a8f39d9dba6
https://github.com/user-attachments/assets/6c2b5a13-cc9f-43ca-bff1-944c5b318a92
Community
Bug reports, feature requests, and pull requests are welcome. Feel free to open an issue or PR.
If you find this plugin useful, please give it a star on GitHub. It helps others discover it.
License
MIT
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.