Auto Pin
pendingby Kageetai
Automatically pins tabs when they are opened.
Auto Pin for Obsidian
Automatically pin tabs when they are opened in Obsidian.
Features
- Automatic pinning - Tabs are pinned automatically when opened
- File type control - Choose which file types to auto-pin:
- Markdown notes (.md)
- Canvas files (.canvas)
- Bases (database views)
- Other file types (PDF, images, etc.)
- Folder exclusions - Exclude specific folders from auto-pinning
- Manual commands - Pin or unpin all tabs at once
Installation
From Obsidian Community Plugins
[!IMPORTANT] Not yet available on the Community Plugins page (PR pending)
Using BRAT
- Install the BRAT plugin from Community Plugins
- Open BRAT settings and click "Add Beta plugin"
- Enter the repository URL:
Kageetai/obsidian-plugin-auto-pin - Click "Add Plugin" and enable it in Settings → Community Plugins
Manual Installation
- Download
main.js,manifest.json, andstyles.cssfrom the latest release - Create a folder named
auto-pinin your vault's.obsidian/plugins/directory - Copy the downloaded files into the folder
- Reload Obsidian and enable the plugin in Settings → Community Plugins
Settings
| Setting | Default | Description |
|---|---|---|
| Enable auto-pin | On | Master toggle for automatic pinning |
| Pin existing tabs on load | Off | Pin all open tabs when the plugin loads |
| Pin Markdown notes | On | Auto-pin .md files |
| Pin canvas files | On | Auto-pin .canvas files |
| Pin bases | On | Auto-pin database views |
| Pin other file types | Off | Auto-pin PDFs, images, etc. |
| Excluded folders | Empty | Comma-separated folder paths to exclude |
Commands
- Pin all open tabs - Manually pin all currently open tabs
- Unpin all tabs - Remove pins from all tabs
Development
# Install dependencies
npm install
# Build for development (watch mode)
npm run dev
# Build for production
npm run build
# Run linter
npm run lint
License
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.