Requires Paseo 0.9.1–0.9.x and Node.js/npm on the machine running the Paseo daemon.
\npaseo plugin install npm:paseo-auto-pin@0.4.0\nOr install from GitHub:
\npaseo plugin install https://github.com/stv1024/paseo-auto-pin\nOpen Auto-Pin in the sidebar to adjust your settings. It starts with auto-pin\non for all new workspaces.
","readmeText":"# Auto-Pin for Paseo\n\nAutomatically pin new [Paseo](https://paseo.sh) workspaces, with exceptions for individual projects.\n\nKeep everyday work near the top of your sidebar and leave experiments unpinned.\nAuto-Pin runs in the background, even when its panel is closed.\n\n\n\nCreate a workspace. Auto-Pin moves it into **Pinned** automatically.\n[Watch the original video](docs/demo.mp4).\n\n## Install\n\nRequires **Paseo 0.9.1–0.9.x** and Node.js/npm on the machine running the Paseo daemon.\n\n```bash\npaseo plugin install npm:paseo-auto-pin@0.4.0\n```\n\nOr install from GitHub:\n\n```bash\npaseo plugin install https://github.com/stv1024/paseo-auto-pin\n```\n\nOpen **Auto-Pin** in the sidebar to adjust your settings. It starts with auto-pin\non for all new workspaces.\n\n## Choose what gets pinned\n\nThe **Pin new workspaces by default** switch sets the behavior for projects\nwithout an override. Each project has three choices:\n\n| Rule | What happens when you create a workspace |\n| --- | --- |\n| **Follow default** | Uses the current default switch. |\n| **Always** | Pins it, even when the default is off. |\n| **Never** | Leaves it unpinned, even when the default is on. |\n\nFor example, set your main project to **Always**, experiments to **Never**, and\nleave everything else on **Follow default**.\n\nProjects appear automatically from Paseo. You can search by name or folder path.\nRules apply to new workspaces belonging to that project, including worktrees.\n\n### A few things to know\n\n- Changes save automatically and are shared by clients connected to the same daemon.\n- Rules only affect workspaces created afterward. Existing pins stay as they are.\n- Restoring an archived workspace does not pin it again.\n- Auto-Pin never removes a pin. You can still pin or unpin workspaces yourself.\n- **Always** and **Never** override the default switch. To pause the entire plugin,\n disable it in Paseo's plugin settings.\n\nIn the Command Center, use **Auto-Pin: Toggle Default** for a quick change, or\n**Auto-Pin: Open Panel** to manage project rules.\n\n## Update\n\nFor an installation from npm or Git:\n\n```bash\npaseo plugin update auto-pin --check\npaseo plugin update auto-pin\n```\n\nUpdating from 0.3 keeps your existing on/off setting. Every project starts on\n**Follow default** until you choose otherwise.\n\nAuto-Pin **0.4.x** supports Paseo **0.9.1–0.9.x**.\nFor Paseo 0.8, use Auto-Pin 0.2.0; for Paseo 0.7, use 0.1.0.\n\n## Need a hand?\n\nIf a new workspace is not pinned, check its project rule and the default switch.\nIf you just changed a setting on another device, press **Refresh** in the panel.\n\nFor errors or unexpected behavior, [open an issue](https://github.com/stv1024/paseo-auto-pin/issues).\nInclude your Paseo and Auto-Pin versions, the rule you selected, and what happened.\nLogs are available with `paseo plugin logs auto-pin`; remove private paths before\nsharing them.\n\nHave a workflow this does not cover? Describe it in an issue. A concrete example\nhelps decide what to build next.\n\n[Share your workflow in the Paseo community discussion](https://github.com/getpaseo/paseo/discussions/5346).\n\n[What's changed](CHANGELOG.md) · [Development](docs/development.md) · [Community post and demo guide](docs/community.md)\n\n## License\n\n[MIT](LICENSE)\n"}