New Plugin: AI

[shamanicvocalarts]

AI is a Flow Launcher plugin for querying LLM from Flow Launcher via OpenRouter

[cibere]

Hello, and thanks for the plugin submission. If you don't mind, I have a couple of changes that I would like you to make.

1. Could you add the json file extension to the file you made in this PR?
2. It seems like you just copy pasted the contents from your plugin.json file. However, data provided in this repository is slightly different than the data in your plugin.json file. Here is a template that you can use:

{
  "ID": "Unique GUID from your plugin.json",  
  "Name": "Plugin name",
  "Description": "Short description",
  "Author": "Author",
  "Version": "Version from your plugin.json",
  "Language": "Programming language",
  "Website": "Plugin website",
  "UrlDownload": "URL to download",
  "UrlSourceCode": "URL to source code",
  "IcoPath": "Plugin icon image's CDN URL, e.g. https://cdn.jsdelivr.net/gh/Flow-Launcher/Flow.Launcher/Plugins/Flow.Launcher.Plugin.Explorer/Images/explorer.png"
}

4. Could you change the name to something more descriptive? Perhaps OpenRouter AI?
5. Could you add the api key to the settings template? Supporting the env variable is fine, however it would be best to have a unified settings experience between all plugins if possible. There is a password field that would work well here.

[shamanicvocalarts]

Hi, happy to make those changes, sorry for 1 & 2 my bad 😅.

for name, I am happy to change it , though I am intending to support more than openrouter for platform/features in the future with this plugin.
open-webui for instance , for opening initial query in a chat window .
open-webui & ollama for embeddings & knowledge collections .

maybe a name like AI assistant may be more suitable?

happy to add API key field back in

[cibere]

for name, I am happy to change it , though I am intending to support more than openrouter for platform/features in the future with this plugin. open-webui for instance , for opening initial query in a chat window . open-webui & ollama for embeddings & knowledge collections .

maybe a name like AI assistant may be more suitable?

Perhaps, though the only reason I asked for the change was to help differentiate the AI plugins (there are so many different ai models that the name AI could be confusing/misleading). If you are planning to add those other models though, then I'm unsure what a good name would be.

[shamanicvocalarts]

for name, I am happy to change it , though I am intending to support more than openrouter for platform/features in the future with this plugin. open-webui for instance , for opening initial query in a chat window . open-webui & ollama for embeddings & knowledge collections .
maybe a name like AI assistant may be more suitable?

Perhaps, though the only reason I asked for the change was to help differentiate the AI plugins (there are so many different ai models that the name AI could be confusing/misleading). If you are planning to add those other models though, then I'm unsure what a good name would be.

to clear up any potential confusion, OpenRouter is not a model, instead it aggregates many API/models - so out of the box plugin already supports 100s of different models, via Openrouter you can query openAI, Anthropic, Deepseek & many others. this was why AI felt suitable to me as a name to begin with, as this plugin gives you access to 90% of llm models available on the market.

[cibere]

LGTM, however it still needs to be manually tested with flow

[shamanicvocalarts]

Nice one thanks @cibere , let me know if there's anything I need to do on my side. & sorry for excessive commits, I'm quite new to PR process