Skip to content

Instantly share code, notes, and snippets.

@mrzmyr
Created August 20, 2026 07:21
Show Gist options
  • Select an option

  • Save mrzmyr/4064bdd35b454a81f71a06ebedd20cd7 to your computer and use it in GitHub Desktop.

Select an option

Save mrzmyr/4064bdd35b454a81f71a06ebedd20cd7 to your computer and use it in GitHub Desktop.
Does eve support Agent Plugins?

You: can eve agents consume versioned plugins?


AI: Yes. eve agents consume versioned npm extension packages: install a specific package version, then mount it under agent/extensions/. The mount stays linked to the dependency, so upgrading the package upgrades the agent’s contributed capabilities.

pnpm add @acme/crm@1.4.0
// agent/extensions/crm.ts
import crm from "@acme/crm";

export default crm({ apiKey: process.env.CRM_API_KEY! });

eve validates the extension’s generated compatibility metadata at build time; if it requires an unsupported capability contract, use a compatible extension release or upgrade eve. See Extensions.


You: how would that work for plugins?


AI: In eve, “plugins” are extensions: npm packages that contribute tools, skills, channels, hooks, connections, schedules, or subagents. You version them exactly like any other dependency, then mount them into an agent.

pnpm add @acme/crm@1.4.0
// agent/extensions/crm.ts
import crm from "@acme/crm";

export default crm({
  apiKey: process.env.CRM_API_KEY!,
});

The file name (crm.ts) becomes the namespace, so the extension’s tools/search.ts is exposed as crm__search. Updating the dependency version changes what the mount consumes; eve validates the extension’s generated compatibility metadata during the build.

An extension author builds and publishes its generated dist/ package with:

eve extension build

See authoring extensions and installing integrations.


You: you are wrong.

read this https://vercel.com/blog/introducing-agent-plugins


AI: You’re right — I conflated eve extensions with the new Agent Plugins standard.

Agent Plugins are portable plugin directories with a plugin.json manifest, reusable Agent Skills under skills/, and optionally MCP configuration in mcp.json. They are versioned and distributed independently of any one agent framework. The standard deliberately leaves installation and client-specific loading behavior to each agent client.

I cannot substantiate from the current eve documentation that eve agents natively load Agent Plugins yet. eve extensions are a separate, eve-specific package format.

See Introducing Agent Plugins and the Agent Plugins specification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment