#950·big-AGI

Add saved prompts UI, similar to AI Personas UI, and a button in the chat message entry window to select a prompt from the library.

Author: Slava-256Created Jan 27, 2026Updated Sep 15, 2026
Labelstype: feat

What's happening?

Sometimes specific prompts may be a result of long research and refinement, and you may want to use such prompts multiple times to interrogate different documents or different information present in various chats.

So, it would be convenient if Big-AGI allowed maintaining a library of such prompts, similar to how you can maintain a library of AI Personas (which are essentially a library of system prompts with additional settings).

So there may be a button next to "AI Personas" that opens up "Prompt dashboard", similar to "Persona Dashboard", with similar functionality to Create and edit prompts.

I also propose "Requires attachment" or "ask for attachment" or similarly named option/setting for saved prompts that indicates that a given prompt requires an attachment, so that when a user clicks a button to send or beam a chat message with that prompt, and no files are attached, Big-AGI would automatically open a file attachment dialog, saving user a click.

There may be a further refinement of this option to offer 3 choices:

  • no attachment required
  • attachment required anywhere in the conversation
  • attachment required in the message using this prompt

Similar to AI Personas, Prompts may have "Advanced output hints:", "Variables:" (like AI Personas have on "Instruction" tab), and additional data tab, similar to "Data" tab in AI Personas.

When chatting, I propose to have pre-made prompt selection button above "Attach" button in the chat message entry panel (maybe named "Prompt" or "Prompts"?). Conceptually, it seems like selecting a pre-made prompt is similar to attaching a file. You are simply doing a "copy-paste" style attachment when selecting a pre-made prompt.

Where does this happen?

Big-AGI Pro (big-agi.com)

Impact on your workflow

Medium - Workaround exists

Environment (if applicable)

No response

Additional context

No response