Install
npx eve@latest init my-agentWho it is for
This skill is for people who want a filesystem-first way to build a persistent AI agent: put core capabilities in conventional places so the project is easier to inspect, extend, and run. It also fits people ready to create a new agent directory on this machine and accept the side effects of the official init command.
It does not fit people who only want to try one line in a chat and do not want a new project on disk. The official start command creates a directory, installs dependencies, initializes Git, and starts an interactive terminal interface. If you cannot run npx yet, or cannot accept those writes and the interface start, stay with reading the notes and do not run init.
The official repository is https://github.com/vercel/eve Operate only with commands already written on that page. It is currently in a testing phase; behavior may change.
First attempt in 3 minutes
Follow only this start path written by the official page.
Prerequisite: this machine can run npx, the current working directory may create a new folder, and you clearly agree to one local init. First confirm: running it will create a my-agent directory, install dependencies, initialize Git, and start an interactive terminal interface. If you do not yet want to write to disk or open that interface, do not run the command below.
Install location: open a terminal in the directory where you want the new project, confirm the side effects above, then run:
npx eve@latest init my-agent
Low-risk check: after the command ends, do not rush to change business logic. First open instructions.md in the new directory and check that the file exists and that comments still say it is required and is the always-on system prompt. This is a read-only check.
Success signal: a new directory named my-agent appears, dependencies are installed, Git is initialized, the interactive terminal interface is up, and you can see the required instructions.md. If the directory does not appear or that file is missing, do not invent another installer; go back to the official page and check the command text.
Usage cases
Case 1: Build an inspectable agent project from scratch. The official command npx eve@latest init my-agent creates a my-agent directory, installs dependencies, initializes Git, and starts an interactive terminal interface. It fits people who want a conventional directory structure first, then put capabilities inside. Before acting, confirm the current directory has no folder of the same name. If the source text does not say how to skip the interface or skip Git, do not assume such a switch exists.
Case 2: Inspect and understand the always-on system prompt. In the typical structure the source gives, instructions.md is marked required and is the always-on system prompt. It fits people who, after init, only open that file read-only and confirm where the agent’s default instructions live. Filesystem-first means you can inspect with ordinary files. When the source does not write required relations for other prompt files, do not invent directory duties.
Boundaries
eve is currently in a testing phase and is bound by Vercel testing terms; interfaces and behavior may change. The terms page is https://vercel.com/docs/release-phases/public-beta-agreement Treat that page as authoritative.
Only one start command is written in the source: npx eve@latest init my-agent. Do not invent an installer that never appeared. That command writes a directory, installs dependencies, initializes Git, and opens a terminal interface, so it does not fit a scene that only wants a documentation check and refuses any local write.
The source writes eve as a filesystem-first persistent AI-agent framework, with core capabilities in conventional places. It does not list available clients and does not say how to attach an unnamed coding assistant. instructions.md is marked as the required system prompt, but the full directory tree, deployment, and secret configuration are not expanded in the source; do not fill them in.