eve: A filesystem-first framework for durable AI agents.
What problem it solves
Building agents often requires distributing core capabilities across conventions that make projects harder to inspect and operate. Eve places instructions, tools, skills, channels, schedules, and runtime configuration in conventional filesystem locations so agents can be inspected, extended, and maintained directly.
Key features
Filesystem-based authoring — Agent capabilities are organized in a conventional directory structure, making the project's behavior visible through its files.
Source: README
Typed model-callable tools — Tools are defined as typed TypeScript functions that the model can call, with explicit descriptions and input schemas.
Source: README
On-demand procedures — Skills provide reusable procedures that are loaded on demand instead of being included as always-on instructions.
Source: README
Channels and recurring schedules — Agents can expose message channels and define recurring cron jobs through dedicated files in the project structure.
Source: README
Scaffolded project setup — The initialization command creates a project directory, installs dependencies, initializes Git, and starts the interactive terminal UI.
Source: README, examples
Quick start
Copied verbatim from the project's README.
npx eve@latest init my-agentYou are a concise weather demo assistant. Tell users that the weather data is mocked.npm run devWho it may suit
Inference: This may suit developers who want to author durable agents through familiar project files and typed TypeScript components.
Topics to discuss
Which filesystem conventions are most useful for scaling an agent project beyond the basic scaffold?
How should reusable skills and typed tools be organized as an agent grows?
What workflows would help developers inspect, test, and operate agents more effectively?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/vercel/eve#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…