Vercel's Eve 0.22 wants your AI agents to live as files on disk, not secrets in a config

The release, published July 12 under the Apache-2.0 license, is the newest point release in Eve's 0.22 line. Developers scaffold a new project by running npx eve@latest init my-agent, which generates a conventional folder structure: an instructions.md file holding the agent's system prompt, a tools folder for typed, Zod-validated functions the model can call, a skills folder for on-demand procedures, a channels folder for integrations like HTTP endpoints, Slack, and Discord, and a schedules folder for cron-triggered tasks. It's a filesystem-as-API approach that makes agent internals trivially inspectable, a design choice that aligns with broader concerns about hidden complexity in AI projects.

Eve supports multiple LLM backends through configuration, so a project isn't locked to a single model provider. The framework also includes built-in human-in-the-loop prompts, letting an agent pause and ask a person to make a decision rather than guessing, and subagent support, allowing one agent to delegate work to another and incorporate the result. A terminal-based development interface lets developers watch an agent execute a task in real time. This orchestration capability matters because OpenAI's own research shows agents work better in coordinated groups.

The project has drawn 3,500 GitHub stars and 300 forks since launch, with 120 open issues against 132 pull requests. Vercel's documentation for the framework is hosted separately at eve.dev, and generated project scaffolds ship with local documentation under node_modules/eve/docs. The open-source licensing and docs-first approach put Eve in the same philosophical camp as OpenManus's invite-free, no-gimmicks framework.

Eve is one of several recent releases betting that removing configuration overhead, rather than adding features, is the more useful direction for agent tooling, alongside IBM's CUGA framework and the broader push toward file-based, inspectable agent instructions seen in projects like Matt Pocock's Claude Code skills repository. The filesystem-as-interface pattern, for instance, echoes Mistral's shift toward cloud-based coding agents that reduce local configuration burden. Whether developers adopt Eve at scale will depend less on star counts and more on whether the filesystem approach translates to fewer headaches in production, a question ultimately measured in human hours saved.