Automatically pin new Paseo workspaces, with exceptions for individual projects.
Keep everyday work near the top of your sidebar and leave experiments unpinned. Auto-Pin runs in the background, even when its panel is closed.
Create a workspace. Auto-Pin moves it into Pinned automatically. Watch the original video.
A 17-second overview of automatic pinning, project rules, and installation.
Requires Paseo 0.11 or later and Node.js/npm on the machine running the Paseo daemon. For Paseo 0.9.1 to 0.10.x, install Auto-Pin 0.4.2 (see Update).
Install the reviewed version from the official plugin registry:
paseo plugin add stv1024/auto-pinYou can also install directly from npm or GitHub:
paseo plugin install npm:paseo-auto-pin@0.5.2
paseo plugin install https://github.com/stv1024/paseo-auto-pinThe registry can lag behind npm for a few days while each new version is reviewed. Paseo 0.11.x and 0.12.x have a known sidebar synchronization issue that can temporarily hide a newly applied pin. Paseo 0.13.0 fixes it.
The Auto-Pin row in the sidebar header shows the default switch. Click the switch to turn auto-pin on or off. Click the row to open the panel with project rules. Auto-Pin starts on for all new workspaces.
The Pin new workspaces by default switch sets the behavior for projects without an override. Each project has three choices:
| Rule | What happens when you create a workspace |
|---|---|
| Follow default | Uses the current default switch. |
| Always | Pins it, even when the default is off. |
| Never | Leaves it unpinned, even when the default is on. |
For example, set your main project to Always, experiments to Never, and leave everything else on Follow default.
Projects appear automatically from Paseo. You can search by name or folder path. Rules apply to new workspaces belonging to that project, including worktrees.
- Changes save automatically and are shared by clients connected to the same daemon.
- Rules only affect workspaces created afterward. Existing pins stay as they are.
- Restoring an archived workspace does not pin it again.
- Auto-Pin never removes a pin. You can still pin or unpin workspaces yourself.
- Always and Never override the default switch. To pause the entire plugin, disable it in Paseo's plugin settings.
In the Command Center, use Auto-Pin: Toggle Default for a quick change, or Auto-Pin: Open Panel to manage project rules. While a workspace is open, you can also set its project's rule directly with Auto-Pin: Always Pin This Project, Auto-Pin: Never Pin This Project, or Auto-Pin: This Project Follows Default.
For an installation from the registry, npm, or Git:
paseo plugin update auto-pin --check
paseo plugin update auto-pinUpdating from 0.3 keeps your existing on/off setting. Every project starts on Follow default until you choose otherwise.
Auto-Pin 0.5.2 has been integration-tested with Paseo 0.11.1, 0.12.0, and 0.13.0. Future versions are allowed, but compatibility still depends on Paseo keeping the APIs this plugin uses. Paseo 0.10 and earlier reject the 0.5 manifest. For Paseo 0.9.1 to 0.10.x, use Auto-Pin 0.4.2:
paseo plugin install npm:paseo-auto-pin@0.4.2Auto-Pin 0.4.0 is restricted to Paseo 0.9.1–0.9.x. For Paseo 0.8, use Auto-Pin 0.2.0; for Paseo 0.7, use 0.1.0.
If a new workspace is not pinned, check its project rule and the default switch. If you just changed a setting on another device, press Refresh in the panel.
If a workspace appears pinned, disappears from Pinned, and returns later on Paseo 0.9.2 to 0.12.x, update Paseo to 0.13.0 or later. See the known issue and its fix. The daemon retains the pin; updating or reloading Auto-Pin does not fix this host issue. The panel's Refresh button only refreshes plugin settings and projects, so it does not repair the sidebar state. Upstream fix: getpaseo/paseo#7758, for getpaseo/paseo#5447.
For errors or unexpected behavior, open an issue.
Include your Paseo and Auto-Pin versions, the rule you selected, and what happened.
Logs are available with paseo plugin logs auto-pin; remove private paths before
sharing them.
Have a workflow this does not cover? Describe it in an issue. A concrete example helps decide what to build next.
Share your workflow in the Paseo community discussion.
What's changed · Development · Community post and demo guide