Extend eve agents with installable extensions
Vercel just turned agent extensibility into a package manager problem. Extensions ship, version, and upgrade like dependencies.
Why it matters
Vercel's eve platform now supports installable extensions for agents, enabling reusable tools, skills, and hooks across any agent. This commoditizes agent composition and lowers barriers for builders to package and distribute agent capabilities at scale.
The key facts
13 to knowExtensions can package tools, connections, skills, instructions, and hooks
Extensions publish to package registries with versioning and upgrade support
Single-command scaffolding: 'eve extension init'
Extensions imported as file-based namespaced modules in agent/extensions/
Approval-gating for tool execution via disableTool()
Config schema validation using standard libraries like Zod
Tool result type narrowing in hooks via toolResultFrom
Supports domain-specific extensions: browser-use, memory, self-improvement patterns
Eve extensions support tools, connections, skills, instructions, and hooks
Extensions published to package registries with versioning and upgrade paths
Namespace-based extension isolation (e.g., crm__search tool naming)
Tool approval controls and result type narrowing via hooks
Vercel product announcement; shipped July 21, 2026
Go to the source
Vercel Blogvercel.com
Publisher excerpt: You can now package tools, connections, skills, instructions, and hooks into extensions that any agent can import. Extensions can be published to package registries, then installed, versioned, and upgraded like any other project dependency.eve A browser-use extension might ship tools for navigating…