eve-agents extensions package-management dependency-composition tool-isolation

Eve agents now support installable extensions

Package tools, connections, skills, and hooks as versioned dependencies; install extensions like npm modules with schema validation and tool-level access control.

Summary

Reduces boilerplate for agent capability reuse across projects and teams. Enables composition patterns familiar to web developers (install → import → configure), speeding up agent scaffolding and maintenance.

Why it matters

Implementation verdict

Replaces inline tool definitions with external packages. Requires `npx eve@latest extension init` to scaffold, then `eve extension build` to publish. Ready now—use `agent/extensions/` directory pattern for namespace isolation and `disableTool()` for fine-grained access control.

Sources

1.You can now package tools, connections, skills, instructions, and hooks into extensions that any eve agent can import
2.The filename sets the namespace, so the extension's search tool runs in the agent as crm__search
3.Declare a config schema using a standard schema library, such as Zod
4.eve extension build generates the publishable package

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs