Durable prompt drafts for Paseo: write an instruction carefully, refine it over days, send it to one agent or several, and read back exactly what each one received. A draft belongs to no session, tab, or workspace, and it outlives all of them.
This is a Paseo plugin. It runs on any Paseo 0.8 host without a custom build of the daemon or the app, and its client runs in every connected app, phones included.
Requires Paseo 0.8.0-beta.1 or later on both the daemon and the app.
- Enable plugins on the host under Settings → Plugins (or set
"pluginsEnabled": truein the daemon'sconfig.jsonand runpaseo reload). - Install from GitHub:
paseo plugin add custyhs/paseo-draftsPin a release with --ref v0.1.0, and target another daemon with the global --host <url> option. Update later with paseo plugin update paseo-drafts.
Drafts appears in the sidebar, Scratchpad in the workspace tab launcher and the Explorer, and the plugin's settings under Settings → Plugins → Drafts.
Plugins are trusted, unsandboxed code. The server half of this plugin runs on the daemon host with the daemon user's access. Read the source before installing.
- Drafts surface. Create, edit, search, and archive drafts. Search covers current text and every revision you ever sent, and says which revision matched.
- Autosave with a conflict choice. A pause in typing earns a write; the editor shows saved, saving, not saved, or changed elsewhere, and never claims saved for text the host has not accepted. When another client edited the same draft you choose reload or overwrite.
- Plans and derived status. A draft can be planned for several workspaces, or for a project when the worktree does not exist yet. "Planned here" is derived: planned for this workspace and the current revision not yet sent there. Sending moves it to history; editing afterwards brings it back with unsent changes.
- Sending with an immutable snapshot. Each send freezes a byte-exact copy of the body, delivers it to a new agent (you pick provider and model) or an existing session, and records the outcome. A failed send keeps the snapshot and says why.
- Scratchpad panel. Inside a workspace: what is planned here, what has run here, and a place to write the next instruction while the current one runs.
- Web checkpoint. In a browser or the desktop app, text the host has not accepted is kept in IndexedDB without expiry, restored when you reopen the draft, and retried until the host takes it. iOS and Android keep it only while the app stays open. Paseo hides plugin surfaces while a host is disconnected, so you reopen the draft once the host is back.
- English and Simplified Chinese. Automatic by device language, or pinned in the plugin's settings.
Drafts live on the daemon host under $XDG_CONFIG_HOME/paseo/drafts, which is ~/.config/paseo/drafts when XDG_CONFIG_HOME is unset. One directory per draft:
drafts/
└── drf_<id>/
├── artifact.json # mutable; the only file an edit rewrites
├── snapshots/0007.json # written once per sent revision, never rewritten
└── dispatches.jsonl # append-only send log
The layout matches the files written by the drafts feature of the custyhs/paseo fork, so a directory copied from that fork's $PASEO_HOME/drafts reads unchanged.
Change the directory under Settings → Plugins → Drafts. The override is stored in ~/.config/paseo/paseo-drafts.json on the host; changing it opens the other directory without a restart and moves no files. A directory the daemon cannot read is reported on every draft operation, with its path, instead of showing an empty list.
The plugin sandbox has no equivalent for four things the built-in feature did:
| Built-in feature | Plugin |
|---|---|
| One list across every connected host | One host at a time; the header host picker switches when several have the plugin |
| Read permission for reads, manage for writes | Every operation needs the host's manage permission |
| Offline checkpoint on every platform | Web and desktop only |
| Live push of other clients' changes | Polled every 15 seconds while a surface is open; your own writes show immediately |
npm install
npm run typecheck
npm test # node --test, no bundler
paseo plugin install /absolute/path/to/paseo-drafts
paseo plugin reload paseo-drafts # after every source change
paseo plugin logs paseo-draftsLayout follows the Paseo plugin scaffold: shared/ holds Zod records, RPC contracts, and the settings definition; server/ holds storage, search, and the host-side send; client/ holds the React Native surfaces, the save loop, and the checkpoint. Relative imports carry .ts extensions so the same files run under Node's test runner and Paseo's plugin compiler.
MIT