DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build and hot-reload a Vetta plugin outside the source repo with Open Vetta

Scaffold a plugin, install it into the running desktop app, and watch changes live.

Remote script. Plugins run inside the desktop renderer and are treated as curated code, not an arbitrary-code sandbox, so review any plugin's code and permissions before installing it.

Who it is forA developer or coding agent that needs to add a custom desktop UI feature, file handler, message action, or tool to Vetta without cloning the Vetta source.

The problemExtending a desktop agent usually means forking its source tree, which is slow to set up and hard for an agent to work inside.

The outcomeA working plugin project with an AGENTS.md file, built and installed into the desktop app, with hot reload during development.

What you need first

  • Download the desktop app for macOS, Windows, or Linux, or run from source with Bun 1.3+ and Node.js 20+
  • An API key for a supported provider, an OpenAI-compatible endpoint, or a local inference server (BYOK)
  • A local project folder or documents to work on

Steps

  1. Run npx @vetta-org/plugin-cli init --id my-plugin --name "My Plugin" in an empty parent directory.
  2. Run cd my-plugin && npm install to enter the project and install its dependencies.
  3. Run npx vetta-plugin-cli docs to find the plugin manual and the SDK version it documents.
  4. Run npm run install:vetta to build, package, and install the plugin into the running desktop app.
  5. Run npx vetta-plugin-cli watch so the host loads the plugin from this directory and reloads on change.

Prompt for your agent

Using the Open Vetta plugin CLI from the open-vetta project, scaffold a plugin named <plugin-id> in <parent-directory>, then add a small capability declared in plugin.json. Report the output of `npx vetta-plugin-cli docs` and confirm the plugin installs with `npm run install:vetta`. Verify that the declared capability appears in plugin.json and is limited to what the task requires.

Caveat. The README says plugins should be treated as curated code, so read the plugin trust and permission model before distributing one.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page