Instructions: Your Agent's Brain
Start an Eve project with npx eve init and write instructions.md — the always-on Markdown that defines who your agent is and how it behaves.
What it is#
An Eve agent begins as a folder. The single most important file is instructions.md — a Markdown document that tells the model who it is and how it should behave. It is the always-on system prompt.
Why you'd care#
You can get a talking agent with zero TypeScript. Instructions are where you set tone, scope, and guardrails before any code exists.
Before#
An empty directory. No agent, no behavior.
After#
Scaffold the project and write your first instructions:
npx eve@latest init my-agent
cd my-agent
# Identity
You are a personal research assistant. You help the user understand
topics by giving grounded, citation-friendly answers.
# Guardrails
- Never invent facts. If you don't know, say so.
- Prefer primary sources and clearly separate facts from opinion.
Run it:
eve dev
Then ask: "What's the difference between durable and ephemeral execution?" — the agent answers from its instructions.
Do it yourself#
- Run
npx eve@latest init my-agentandcd my-agent. - Open
agent/instructions.mdand set an identity plus two guardrails. - Run
eve devand hold a short conversation. - Confirm the agent stays in character and respects your guardrails.
Gotchas#
instructions.mdis always in context — keep it specific, not a novel.- The filename matters:
instructions.mdis the reserved name Eve discovers automatically.
Recap#
instructions.md is your agent's brain. One file, one npx eve init, and you have a talking agent. Next, we choose its model.