한국어Download

Plugins

Extensions from git, reviewed before they install

Plugins, MCP servers, skills, agents, themes, fonts, languages, model providers and messaging connections all arrive the same way: from a git repository or a folder, installed after you review the source and its hash.

The install review for the Nord theme package showing its source folder, contents hash, compatibility and an Install button
The Marketplace tab’s Add menu: Add marketplace, Install from Git URL or folder, Add MCP server, Create a plugin, Install from file

Ways in

Marketplaces, git addresses, folders and files

From the Marketplace tab’s Add menu, add a marketplace repository, or install one package straight from a git address or a folder.

  • Official. Built into Ave, and the only source whose plugins can be granted host secrets.
  • Managed. Added by an organisation through marketplaces.additional in the machine policy file.
  • Custom and direct. Add a repository in Settings → Marketplace → Add, or install one git folder as one package.
  • Install links. An ave://install link only opens a confirmation screen; nothing installs until you confirm.

Installing

What you review is what installs

The install plan is bound to the hash of what you reviewed. If the folder changes in the meantime, what installs is still what you reviewed, and the plan expires after a few minutes.

The review step of Install from a git address or folder: a theme package that runs no code

Check the address

First it shows what kind of package this is, whether it runs code, and where it comes from.

The install plan for Nord 1.0.1, bound to the folder’s contents hash, with the time left before it expires

The install plan

“What you review here is what installs”, with the contents hash and when the plan expires.

The color theme list in Theme settings with Moonstone, Gallery and the Tokyo Night theme installed from the marketplace; the dark version shows Tokyo Night turned on

Themes apply right away

An installed theme appears in Theme settings marked as coming from the marketplace. The dark picture shows the Tokyo Night theme turned on.

The Model settings with a More providers in Marketplace button at the top right

Providers are packages too

A model provider that isn’t built in is added as a marketplace package.

Official marketplace

What the official catalog holds

The official marketplace is the git repository ken-jo/agent-marketplace, and its marketplace.json lists every package. The counts and names below are read from that file at a recorded commit.

399 packages · catalog commit 1f21a1839dcb

  • 3

    Plugins

    Hello World · Ave Local Indexer · Ave Meeting

  • 1

    Agent plugins

    Meeting Notes Kit

  • 23

    MCP servers

    AWS KB Retrieval MCP · Brave Search MCP · Browserbase MCP · Context Mode MCP and 19 more

  • 153

    Skills

    Angular Architect · Api Designer · Architecture Designer · Atlassian Mcp and 149 more

  • 169

    Agents

    Anthropologist · Geographer · Historian · Narratologist and 165 more

  • 35

    Model providers

    AI Hub Mix Provider · AskSage Provider · Azure AI Foundry Provider · Baseten Provider and 31 more

  • 14

    Themes

    Catppuccin Latte · Catppuccin Mocha · Cherry Blossom · Executive Graphite and 10 more

  • 1

    Languages

    한국어 (Korean)

  • Pinned to commits. Every catalog version names the git commit it installs from, and the install is bound to that commit.
  • Code ships as a release archive. A plugin version names its release archive and that archive’s SHA-256, so the catalog pins the exact bytes.
  • Compatibility is declared. Each version states the oldest Ave it needs; a version that needs a newer Ave is not installed.
  • So is network access. A plugin lists the hosts it may reach (sixteen at most), and the catalog carries that list.

For people who build them

Two ways to run

An entry plugin is a JavaScript module; a process plugin is a program in any language that talks to the host over JSON-RPC on standard input and output. Process plugins need the OS sandbox and are not supported on Windows.

Staged releases

Publishers can yank a version or roll it out to a share of installs first, and you can opt into canary versions with the canaryOptIn setting.

Alerts by kind

Each alert kind a plugin declares starts on or off at install as the plugin chooses, and you can switch each kind off. Alerts keep to cooldowns and rate limits, as cards or system notifications. A conversation a plugin suggests starts only when you accept it.

Questions

Do plugins run inside the app?

No. Whatever way they were installed, every plugin runs in its own process outside the app, and inside the sandbox when it is on. If one fails to start, the others keep working.

Can a plugin reach any site?

Only the domains it declares in networkAccess.allowedDomains, sixteen at most. The host sends one hop at a time and checks every redirect.

What if installed files change?

Each install writes a receipt with a SHA-256 per file, checked again at launch. A plugin that doesn’t match is not loaded.

Are updates automatic?

New versions are checked at launch and on a schedule, and applied one at a time while the conversation is idle. If permissions, MCP servers or hooks differ from what you approved, the update waits for your review.

Can an organisation manage installs?

A policy file sets allow and block lists, default installs and required installs. A required package cannot be uninstalled or disabled.

Are there limits on marketplace addresses?

Plain http and internal-network addresses ask once; metadata and other unsafe addresses are always refused.

How do I try a plugin I’m building?

Run an unpackaged build with AVE_DEV=1 and choose Settings → Extension Settings → Developer tools → Install from local folder.

Read on