Run your QuickAdd choices from Raycast. The forms, the pickers, and the finish message are Raycast's. The work is QuickAdd's, running inside Obsidian through Obsidian's command-line interface. I write QuickAdd, and this is its official Raycast extension.
Install it from the Raycast Store. The extension's README shows what it can do and what it needs.
extension/is the extension, and the only folder that ships to the store.demo-vault/is the vault in the pictures.scripts/setup-demo-vault.shdownloads the QuickAdd release it expects.e2e-vault/has one QuickAdd choice per field kind and a macro script that raises every script prompt.scripts/e2e-protocol.mtsdrives them all through the real plugin.- ARCHITECTURE.md has the protocol, the vault lookup, and the reasons behind each choice.
cd extension
npm install
npm run dev # ray develop: installs into Raycast in watch mode
npm run lint # ray lint: manifest, code, and store screenshots
npm test # unit tests for field parsing, completion, and the run state machine
npm run buildFor the end-to-end run, build QuickAdd in ~/Developer/quickadd (or set QUICKADD_DIR), run scripts/setup-e2e-vault.sh to copy the plugin in, and open e2e-vault/ in Obsidian once with Open folder as vault. Then, from the repo root:
node --disable-warning=MODULE_TYPELESS_PACKAGE_JSON scripts/e2e-protocol.mtsIt runs every choice through quickadd:interactive, answers each prompt the way the extension would, and checks the notes QuickAdd writes to e2e-vault/Output/.
To open a choice against either vault from a deeplink, URL-encode {"vaultPath":"<repo>/demo-vault","choiceId":"quick-capture"} and append it as ?context= to raycast://extensions/christian_bager_bach_houmann/quickadd/run-choice.
npm run publish in extension/ updates the store submission.
