My most-used use case is Recall for YouTube summaries. I love the convenience of the extension interface discretely to the side, and it's very quick and easy to select one of the two standard Actions.

However, my ideal is to create my own extended quick Actions, or otherwise modify the standard Action prompts to include enhancements something like "If the YouTube video title or thumbnail is click-baity, emphasize a concise answer to the click-bait question in the very first paragraph of your summary" and/or "if the video title/thumbnail references a list of things, emphasize a summarized and enumerated list of those things in the very first paragraph of the summary".

Among other things, the bottom line is just to get to the bottom line simply by pressing the quick Action link (i.e. not necessarily just in the chat or notebook) ... then I can decide to what degree I want to invest in consuming/reading/watching the rest of the content.

I clearly prefer option A (in chat), because it allows an iterative flow of learning, especially important for generating questions, detecting errors and refining knowledge within the same conversation.

However, the main problem with option A is the clutter in the chat. The ideal solution would be to maintain activation within the chat, but with structured or collapsible results that do not saturate the conversation.

In addition, it would be very useful to be able to directly convert the results into notes or cards, since the actual use is iterative and based on continuous improvement.

Option B (Standalone) would be my go-to, since most use cases I'd have for Custom AI Actions or Slash Commands would start from a fresh chat.

That said, Option A makes sense too — and honestly, where I need it most is inside a card. Like, if I've added a YouTube video to Recall, the transcript is basically already loaded, and when I open that note and go to the note's chat, I want to be able to use Custom Actions with Slash Commands right there too.

Option A: In-chat is non-negotiable. Option B: Standalone is a nice-to-have as a clean-start affordance, not a restriction. The "clutter" concern is better solved with collapsible action outputs or a visual separator, not by killing context continuity.

The bigger design question is what context an action operates on. Real workflows need more than "current message" or "full thread." A long research chat might span multiple topics, and I'd want to run "extract key arguments" against only the relevant cluster of messages, not everything. Even a lightweight "apply to: full chat / recent messages / selected" toggle at trigger time would make a real difference. Potential to turn a saved-prompt shortcut into something people build workflows around, and where Recall could pull ahead of competitors offering canned prompt templates. Just my 2c.

Both x

Ideally, it should be a mix of option A and B that you suggested. We should be able to set any of the custom prompts as a default prompt, and also use the other non-default prompts in mid-chat.

If that's not possible and I'd have to choose just between A & B, then I'd prefer option A. We should be able to add more than 1 custom instruction overall. Ideally, the slash command mid-chat would work better.

Snipd does this really well!