Pastepile

Update an existing Pastepile memory while preserving its previous content in version history. Use this for conversation snapshots: after significant growth, a debugging breakthrough, an architecture decision, a large code generation, or before context compaction. With an API key configured, it can checkpoint any paste that same key created without the one-time edit_key. Otherwise pass the edit_key returned by pastepile_save. Reusing one slug avoids duplicate memories while keeping every prior checkpoint recoverable from the paste's version history.

Permanently delete a paste from Pastepile. Use this when the user asks you to forget, remove, or delete something you saved earlier. With an API key configured you can delete any paste that was saved with that key, WITHOUT the one-time edit_key, which is what makes saved memory reversible across sessions. A paste saved with no key (or by someone else) needs its edit_key passed explicitly. Deletion is immediate and permanent: there is no undo and no trash. Confirm with the user before forgetting anything they did not just ask you to forget.

Retrieve a previously saved paste or memory in full, by slug, full Pastepile URL, or the `session` a memory was saved under. Returns the title, language, and file contents. Use this after pastepile_recall when a preview is not enough. An ENCRYPTED MEMORY of your own is decrypted here on this machine with the key in your Pastepile state directory; if that key is missing or wrong this says so rather than returning ciphertext. Password-protected and burn-after-read pastes, and encrypted pastes belonging to someone else, are not retrievable through this tool.

List recent Pastepile pastes. With an API key configured this defaults to scope "mine": YOUR saved pastes, newest first, including unlisted ones. Use scope "public" for the public feed. For targeted lookups use pastepile_search instead.

Back up, check, and restore the key that opens your encrypted memories. Pastepile does not have this key and cannot reissue it, so a machine that loses it loses those memories permanently. Use `status` to see whether a key exists here, `backup` to write a copy to a path the user gives you, `verify` to confirm a backup file still matches, and `restore` to install a key on a new machine. NONE of these ever returns the key itself: it would land in this conversation and in whatever logs the conversation reaches. Tell the user the file path and let them move the file.

Search YOUR OWN memory (everything saved with the configured API key) by text, tag, and kind, newest and most relevant first. Use this at the start of a session when the user refers to earlier work, and before asking them to repeat context you may already be holding. Returns titles, previews, sessions and URLs, not full bodies; fetch one with pastepile_get when you need all of it. With an API key this searches that key's memory from any machine; without one it searches the trial memory this device saved.

Save the current state of your work to durable memory, keyed by a session name YOU choose. This is the primary tool: prefer it over pastepile_save for anything you may want back later. The first call under a session creates the memory; every call after updates that same memory and keeps the previous content as a version; a call whose content is unchanged does nothing and costs nothing. You never need to track a slug, a URL, or an edit key between calls, and you must never ask the user for one. Send the WHOLE current memory each time, not a delta. Works without an API key as trial memory (expires a month after its last save, searchable from this device only); a Pro API key makes memory permanent and portable.

Put an earlier version of a memory back as the current one. This is not destructive: what is current now is preserved as a new version first, so a restore can itself be undone. Use it when a memory was overwritten with something worse, or to return to a known-good state after an experiment. Name the memory by `session` or by `slug`, exactly one. With the API key that wrote the memory, any listed version can come back; trial memory (no key) restores the previous save only.

Save text, code, notes, or any knowledge to Pastepile and get back a stable, shareable URL you can retrieve later. Use this as durable memory: whenever you produce output worth keeping across sessions, save it and remember the returned slug or URL. Returns url, slug, raw_url, and edit_key. The edit_key is shown only once and is required to update with a per-paste credential. With an API key configured, pastepile_checkpoint updates a paste that same key saved using only its slug, while preserving the previous revision in history. Deleting is separate: pastepile_forget removes a paste saved with the configured API key using only its slug.

Search Pastepile pastes by keyword and get back matching titles, previews, and URLs. With an API key configured this defaults to scope "mine": YOUR private memory, the pastes saved with that key (titles, filenames, and contents, including unlisted pastes). Use scope "public" to search the global public corpus instead. Without a key only the public scope is available.

Show one memory's full version history plus the memories most related to it. Each entry has a version number, a timestamp, a size and a preview, so you can see how the work changed without downloading every revision. Pass a version number to pastepile_restore to bring one back. Name the memory by `session` if you still know the session name you saved under, which you usually do, or by `slug` if you have it. Give exactly one. With an API key this reads that key's full server-side history; without one it reads this device's trial-memory timeline.