Prompt Library

  • Desktop, mobile and web
  • All plans
View as MarkdownFeature page

What it does

A built-in manager for the prompts you keep retyping: save them once, organize them in folders with tags, and insert or send them in one click, on any agent. Each project has its own library, stored in the repository so teammates who pull get the same prompts, plus a global library that follows your account across every project. A prompt can be marked personal to stay private. Linked prompts let one prompt pull others in when it is copied or sent (see Linked Prompts), a reference token pulls one in at launch time instead of copying it (see Prompt References), and a Community tab browses the prompts other AgentsRoom users have published (see Community Catalog).

Where to find it

  • Inside a project: dock item Prompts library (group Knowledge, "Reusable briefs").
  • Composer toolbar: the Prompts button opens the library; the Save button saves the current draft as a new prompt.
  • In the composer, type a trigger character at the start of a word (configurable; the popover Prompts in the composer lists the current Trigger keys) to open the autocomplete: arrows to navigate, Enter to insert, Esc to dismiss.
  • Command palette (Cmd K / Ctrl K): the "Prompts" group.
  • Modal sidebar: All prompts, folders, Root and a Community tab.

How to use it

  1. Open the library, click New Prompt, give it a title, a body, tags, optionally a folder, a one-line Description ("What this prompt is for, in one line", required to share it) and a Category. Tick Personal prompt to hide it from teammates sharing the project. Cmd/Ctrl+Enter saves.
  2. Reuse: from the composer autocomplete (insert at the cursor), from a card's Copy prompt (clipboard), or by sending it to the focused terminal. A card shows Global prompt, Project prompt or Personal prompt.
  3. Organize: drag and drop between folders, Add subfolder, Duplicate, Copy to <scope> to move a prompt between the project and the global library.
  4. Search: the field searches the current scope; Search globally or the Search scope selector (Auto, This scope) spans project and global, and shows matches from Other projects with Copy to reuse here.
  5. History (editor, existing prompt): every save that changes a prompt (title, body, description, tags, category, linked prompts) keeps the previous version. Pick one to see what restoring it would change, then Restore this version loads it in the editor; save to keep it, the current state stays in the history.

Settings

  • promptShortcutTriggers (global, from the composer's Prompts popover): the characters that open the prompt autocomplete in the composer.
  • composerHiddenActions (global, Settings > Composer > Composer toolbar buttons): hide the Prompt library button.

Agent tools (MCP)

  • prompts_list: the project library plus the account library, with titles, scope, tags, folders, the prompt's handle and a preview; agents are told to check it before asking you to repeat a complex brief.
  • prompts_get: full body, tags and linked prompts of one prompt.
  • prompts_save: save a new prompt; the agent must ask you first. isPersonal keeps it out of git, description and category are the two fields sharing it with the community needs.
  • marketplace_search: search the public catalogs of prompts and skills, read-only. It installs nothing.
  • prompts_update: edit an existing prompt in place (rename, move, add a section) without creating a duplicate.
  • prompts_delete: remove a prompt, only on your explicit instruction.

Providers

All providers, no difference: a prompt is text inserted in the composer or pasted into the terminal, whatever CLI runs there.

Mobile

Present: the Prompt library sheet on the phone lists project and global prompts, with search, New prompt, edit, Send to terminal (to the focused desktop agent) and Share with the team. Personal prompts stay personal there too. The editor also has Version history with Restore this version, applied by the connected desktop.

Limits

  • No cap on how many prompts you store, on any plan: they are text on your disk and they cost nothing to keep.
  • Project prompts are written to .agentsroom/prompts.json in the repository, so they travel with git; personal prompts are kept out of git automatically.
  • No account is needed for a project library; signing in adds cloud sync so the global library and personal prompts follow you across devices.
  • Version history needs a signed-in account (versions are recorded by the server at each synced save) and keeps the last 50 versions of each prompt. Moving a prompt to another folder is not a new version; team-shared prompts have no history.

Common questions

  • Is the library per project or global? Both: one library per project (in the repo) and one global library on your account.
  • Can I share prompts with my team? Commit .agentsroom/prompts.json; everyone who pulls gets them, no account needed. Personal prompts never leave your machine through git.
  • How do I insert a prompt while typing? Type a trigger key at the start of a word in the composer and pick from the list.
  • What is the difference with the Scratchpad? The composer draft is the prompt you are writing now; the library is the permanent, shared collection. Save promotes one into the other.
  • I overwrote a prompt by mistake. Open it, click History, pick the version before the change, Restore this version, then save.
  • Can an agent save prompts for me? Yes, but it must ask first; it can also update an existing one instead of creating a duplicate.

Related