Mael

A first "lighter" version (without including a workflow visualization and construction framework) would be to just define "tasks" (eg addObsidianTodo, searchGoogle) which have a few json parameters from the query,...

BTW could be useful to add some more details on the Swift build: ```sh git clone https://github.com/ggerganov/whisper.cpp.git cd whisper.cpp # if needed, add install required build tools eg brew install...

Should also drag and drop the framework here (`whisper.cpp/build-macos/framework`) in the project settings  and also drag and drop the .dylib from `whisper.cpp/build/src/**.dylib` here in "Build phases" 

(of course we could go fancy and add a MCP server connection, or something, but to be user-friendly for those who don't have all this, perhaps a minimal settings pane...

I coded (with Claude, so dirty) a first implementation which seems to work somehow (but haven't written the code to plug it in actual shell scripts)  you can find...

(this implementation is VERY basic), it would be MUCH better to have some way to constrain the output of the LLM to be json, and to do a lot of...

Example script ```sh #!/bin/bash echo "Args: $WORKFLOW_ARGS" echo "- engine: $WORKFLOW_ARG_ENGINE" echo "- query: $WORKFLOW_ARG_QUERY" echo > /tmp/args.txt

It works :) 

I guess actually we could even implement a way to connect to any MCP server, if we want to have something even more powerful?

No worries! Would you mine telling more about why it doesn't fit in the core direction? Couldn't you otherwise envision a system of "plugins" so at least this could be...