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

How to set up Open Vetta from source and run the desktop app with Open Vetta

Clone the repo, install dependencies, and start the desktop app in development mode.

Who it is forA contributor or developer who wants to modify Vetta or test changes against the dev branch.

The problemContributing to a desktop agent needs a working development environment that does not touch the installed app's data.

The outcomeA running development build of the desktop app that uses its own data folder, with the repo ready for validation commands.

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. Install Bun 1.3+ and Node.js 20+.
  2. Run git clone https://github.com/openvetta/open-vetta.git and then cd open-vetta.
  3. Run git switch dev and then bun install.
  4. Run cd apps/desktop and then bun run dev.
  5. Read QUICKSTART.md for the validation commands and run bun run check:quick before opening a pull request to the dev branch.

Prompt for your agent

Clone openvetta/open-vetta, switch to the dev branch, run bun install, and start the desktop app from apps/desktop with bun run dev. Report whether the app launches and which data folder it uses. Verify that the data folder is ~/.vetta-dev and that the installed-app folder ~/.vetta was not changed.

Caveat. Do not run bare bun test in this monorepo, and use the repository scripts instead, as the README instructs.

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