eve

Why we included this project

eve treats the filesystem as the authoring surface for agents. You build an agent as a directory on disk, write the always-on system prompt in markdown, and put typed tools, on-demand skills, message channels, and cron schedules in TypeScript files at conventional paths. That layout is the contract: what the agent can do and how it is configured is visible just by browsing the project, so it stays easy to inspect and operate as it grows. Teams can start fresh with `npx eve@latest init my-agent` or fold eve into an existing codebase, and because the npm package carries its full documentation, coding agents can read the framework's own docs from `node_modules` without hitting the network.