feat: add prompt-deck extension - #343
Merged
Merged
Conversation
Contributor
|
Pretty cool, I tested with with haiku 4.5 and it works well. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PromptDeck lets you define reusable AI prompts and run them against your selected or
clipboard text. Each prompt can be registered as a Quicklink, so it becomes its own
entry in root search.
Commands
Providers and network access
The only remote hosts contacted are the LLM endpoints the user configures:
api.openai.com,api.anthropic.com,generativelanguage.googleapis.com, or acustom OpenAI-compatible base URL such as Ollama or OpenRouter. No other network
calls are made, and nothing is contacted until the user runs a prompt.
What gets sent is the prompt itself, plus selected and clipboard text when a prompt
opts into them. This is stated in the manifest description and the README's Privacy
section. API keys are stored as Vicinae password preferences, one per provider;
local endpoints that need no auth work with the key left blank. Run history is
stored locally through LocalStorage and can be turned off.
Tested against OpenAI, Google, and an OpenAI-compatible endpoint (OpenRouter).
Notes
media/holds README images only.vici buildbundlesassets/, so they are notshipped to users.