Enable plugins in Settings → Plugins, then install from npm:
\npaseo plugin add npm:@yannelli/paseo-prompt-manager\nThe plugin requires Paseo 0.11.0-beta.3 or later on the daemon and on each app that shows it. Git sync also requires Git on the daemon host.
For Paseo 0.9 and 0.10, install release 0.2.0 with paseo plugin add npm:@yannelli/paseo-prompt-manager@0.2.0. For Paseo 0.8, install 0.2.0 from Git with paseo plugin add yannelli/paseo-prompt-manager --ref v0.2.0.
Open Prompts in the sidebar to manage your library. Paseo provides the plugin's runtime dependencies.
","readmeText":"\n\n# Paseo Prompt Manager\n\nA Markdown prompt library for [Paseo](https://paseo.sh). Create, edit, search, and reuse prompts across agents, with local version history and optional Git sync.\n\n## Install\n\nEnable plugins in **Settings → Plugins**, then install from npm:\n\n```sh\npaseo plugin add npm:@yannelli/paseo-prompt-manager\n```\n\nThe plugin requires Paseo `0.11.0-beta.3` or later on the daemon and on each app that shows it. Git sync also requires Git on the daemon host.\n\nFor Paseo 0.9 and 0.10, install release 0.2.0 with `paseo plugin add npm:@yannelli/paseo-prompt-manager@0.2.0`. For Paseo 0.8, install 0.2.0 from Git with `paseo plugin add yannelli/paseo-prompt-manager --ref v0.2.0`.\n\nOpen **Prompts** in the sidebar to manage your library. Paseo provides the plugin's runtime dependencies.\n\n## Use prompts with agents\n\n- Choose **Prompts** in the agent composer bar to search saved prompts. Each result shows the title and up to four preview lines. Choose a result to send that prompt to the agent. The button shows after the agent starts.\n- Choose **Prompts** in the workspace header to search saved prompts and copy one to the clipboard. It also shows on a **New Agent** tab, where you paste the prompt into the first message.\n- In the composer attachment menu, choose **Saved prompt**. Search by title, filename, or words in the prompt, then attach it to your message.\n- Submit `/prompts` in an agent composer to open the prompt panel.\n- Submit `/prompt code-review` to send `code-review.md` to the current agent and start a turn.\n- From the prompt panel, choose **Send to agent** to send the selected prompt.\n\n### Variables\n\nWrap a placeholder in double braces to fill it in each time you use the prompt. Add a default after a pipe:\n\n```md\nTake a look at {{ module }}, find dead code, and clean it up.\nCreate a Linear ticket from this conversation and assign it to {{ person | me }}.\n```\n\nA name can use letters, digits, `_`, `-`, and spaces, such as `{{ Product Manager }}`. Braces in code spans and code blocks are never variables, so code such as `style={{ flex: 1 }}` or `${{ github.sha }}` is sent as written. Elsewhere, type `\\{{ name }}` for literal braces.\n\nThe editor lists the variables it finds under the Markdown, and **Preview** highlights each one with its default. Choosing a prompt with variables from the **Prompts** button or **Send to agent** opens a form with one field per variable, prefilled with its default. A variable used more than once is asked for once. Fields without a default must be filled in. `/prompt` can't show the form, so it fills in defaults and refuses a prompt with a variable that has none. Attachments contain the prompt as saved, with its placeholders.\n\nAttachment search matches many words across the title, filename, and content. Exact names and title matches appear first, with up to 50 results. Each result shows the title and a one-line preview of the first four body lines. Attachments contain a snapshot of the saved prompt.\n\n## Edit and version prompts\n\nChoose **New prompt**, enter a filename and Markdown content, then save. The first Markdown heading becomes the title. Files keep their normalized names when you edit their content.\n\nOpen **Details** in the editor to add a **Description** and comma-separated **Tags**. Search includes both fields. The folder chip above the list filters by folder and lists tags; the **Archived** chip includes archived prompts.\n\nFolders and subfolders are directories inside the library. Create them from the folder chip or the editor's **Folder** field. Selecting another folder and saving moves the prompt and retains its version history. Nested prompts use paths such as `/prompt engineering/security/code-review`.\n\nUse the expand button to give the editor the available workspace, and the **Edit / Preview** toggle to switch between Markdown and a formatted preview.\n\nBy default, the library lives at `~/.config/paseo/prompt-lib/`:\n\n```text\nprompt-lib/\n├── code-review.md\n└── versions/\n └── code-review/\n ├── code-review.2026-09-09T12-00-00-000Z_v1.md\n └── code-review.2026-09-09T12-05-00-000Z_v2.md\n```\n\nEach save creates a full Markdown snapshot. **History** opens a side panel to inspect a snapshot as source or preview and restore it as a new version. **Archive** removes the current prompt and retains its history; turn on the **Archived** chip to find it, then choose **Restore**.\n\nDescriptions and tags use a `paseo` JSON field in Markdown frontmatter and are included in snapshots. Agents receive the prompt body. Nested history follows `versions/