by openvetta
Open-source, local-first AI agent for coding and real work. BYOK models, MCP, skills, plugins, workflows, and private knowledge bases.
# Add to your Claude Code skills
git clone https://github.com/openvetta/open-vettaLast scanned: 9/18/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-09-18T08:47:42.112Z",
"npmAuditRan": false,
"pipAuditRan": true,
"promptInjectionRan": true
}See how open-vetta compares with popular alternatives.
open-vetta is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by openvetta. Open-source, local-first AI agent for coding and real work. BYOK models, MCP, skills, plugins, workflows, and private knowledge bases. It has 148 GitHub stars.
Yes. open-vetta passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/openvetta/open-vetta" and add it to your Claude Code skills directory (see the Installation section above).
open-vetta is primarily written in TypeScript. It is open-source under openvetta on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh open-vetta against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Open Vetta brings models, project files, local tools, and reusable capabilities into one desktop workspace. Use it for coding, documents, data, research, creative work, and repeatable workflows without giving up control of the environment where the work happens.
It is more than a chat interface: Vetta can inspect a workspace, use tools with visible permission boundaries, produce real files, and keep the execution trail available for review.
| What it means | |
|---|---|
| Local-first workspace | Projects, sessions, files, and execution live in the environment you choose. |
| Bring your own models | Connect supported providers, OpenAI-compatible endpoints, or local inference through BYOK. |
| Real tools and artifacts | Work with code, documents, spreadsheets, media, commands, and generated files in one task flow. |
| Reviewable execution | Tool calls, plans, permissions, progress, results, and recovery paths remain visible. |
| Reusable workflows | Extend the agent with skills, MCP servers, plugins, themes, knowledge, batch tasks, and automation. |
| Open client stack | The desktop app, CLI, SDK, plugin system, themes, mobile client, and IM gateway are developed in this repository. |
| I want to… | Start with |
|---|---|
| Use the desktop app | Download for macOS, Windows, or Linux, then follow installation and first setup. |
| Complete a real task | Follow the first-task walkthrough. |
| Understand the product | Read the product guide and security and data boundaries. |
| Build an extension | Choose between skills, MCP, plugins, themes, SDK, RPC, and CLI. |
| Contribute code | Read QUICKSTART.md and CONTRIBUTING.md. |
Requires Bun 1.3+ and Node.js 20+.
git clone https://github.com/openvetta/open-vetta.git
cd open-vetta
git switch dev
bun install
cd apps/desktop
bun run dev
The development app uses ~/.vetta-dev by default, keeping installed-app data in ~/.vetta untouched. Root-level bun run dev watches core libraries; it does not launch Electron. See QUICKSTART.md for the complete setup and validation commands.
The public documentation has the current task guides and screenshots: browse all product capabilities.
Vetta exposes several extension levels so a simple workflow does not need to become a full plugin:
| Extension | Use it for | Guide |
|---|---|---|
| Skill | Teach the agent a repeatable method or domain workflow. | Abilities |
| MCP | Connect external tools and data over a standard protocol. | MCP connectors |
| Plugin | Extend the desktop UI, files, messages, tools, and host actions. | Plugin development |
| Theme | Replace the visual system and provide theme-specific pages. | Theme development |
| SDK / RPC / CLI | Embed or drive the agent from another application or process. | Developer paths |
You do not need this repository, or a Vetta source checkout, to build a plugin. Nor does an agent:
npx @vetta-org/plugin-cli init --id my-plugin --name "My Plugin"
cd my-plugin && npm install
npx vetta-plugin-cli docs # where the manual is, and which SDK version it documents
npm run install:vetta # build, package, install into the running desktop app
npx vetta-plugin-cli watch # hot reload: the host loads the plugin from this directory
init also writes an AGENTS.md, so any coding agent — Claude Code, Cursor, or Vetta's own —
picks the project up without host-side setup. The plugin manual ships inside
@vetta-org/plugin-sdk, so the contract an agent reads is the contract the project compiles
against; docs locates it rather than anyone hard-coding a node_modules path.
To publish several abilities from one repository, scaffold a marketplace:
npx @vetta-org/plugin-cli init hub --name my-market \
--repository https://github.com/me/my-market --min-app-version 0.55.0
That lays down the index, the abilities/ layout, a repository-level AGENTS.md, and CI running
vetta-plugin-cli sync --check, which keeps .vetta/marketplace.json reconciled with each ability
package. Development commands always act on the nearest ability directory, so working inside a
marketplace is identical to working on a standalone plugin.
Plugins declare capabilities in plugin.json; privileged operations are authorized by the host and checked again at runtime. Plugins run inside the desktop renderer and should be treated as curated code, not as an arbitrary-code sandbox. Read the plugin trust and permission model before distributing one.
A source checkout produces the lite build by default. It has no dependency on a Vetta-operated backend: no account, subscription, remote administration, or hosted marketplace is required. Model requests go to the endpoint you configure, and credentials remain in local credential storage.
Official installers may enable the optional Vetta Serv integration for accounts, subscriptions, and a hosted marketplace. That integration is selected at build time; it is not silently enabled in a lite build.
Local-first does not mean zero network traffic. Model providers, MCP servers, plugins, webhooks, IM integrations, update sources, and optional telemetry can each create their own data boundary. Review:
This is a Bun/TypeScript monorepo with additional Kotlin and Go applications. Dependencies point from applications toward reusable packages; packages/* never depend on apps/*.
| Area | Responsibility |
|---|---|
apps/desktop |
Electron desktop host and renderer |
apps/cli-host |
CLI host for the coding agent |
apps/docs-site |
Next.js documentation site published at docs.openvetta.com |
apps/mobile |
Kotlin Multiplatform Android client |
apps/im-gateway |
Go IM sidecar gateway |
packages/ai · packages/agent |
Provider abstraction and the agent loop |
packages/coding-agent · packages/runtime-* |
Product composition, runtime contracts, tools, storage, MCP, and host adapters |
packages/plugins · packages/themes |
Extension SDKs, presets, and themes |
Architecture details and public integration contracts liv