A bot starts as a name
Pick a face, type what it is called, and start talking. No graph to wire, no config file to learn first.
OPEN SOURCEv0.4 brings remote environments
A minimal, open-source GUI for eve agents. Bring your own key, run it on your own machine, and let your bots keep working after you close the laptop.
Hand work to a bot the way you would hand it to a person: in a sentence, in a thread, from whatever device is in front of you.
They keep the context of every turn, work while the window is closed, and come back when there is something that actually needs you.
Name a bot, give it a job, and let it run. One bot drafts while another watches your inbox and a third sits on a repo you have not opened in a week.
Pick a face, type what it is called, and start talking. No graph to wire, no config file to learn first.
Gmail, Calendar, Slack, Linear, GitHub. Add a plugin once and every bot you run can reach it — with your keys, on your machine.
When a bot needs a key, a scope, or a decision, it stops and asks in the thread — with the options spelled out. Nothing reaches your accounts because a plan looked good.
Evie runs as one environment you own: your files, your keys, your provider CLIs. Reach it from the desktop app, from a browser on the same network, or from anywhere over Tailscale.
The Mac app bundles the server. Nothing to host, nothing to sign up for, no data leaving the machine.
One command serves the same app on your network. Phone on the sofa, laptop at the desk, same threads.
Connect from tryevie.ai to the machine at home and keep driving the bots you left running there.
Start from a suggestion or write the job yourself. The bot keeps that job across every thread, so you stop re-explaining what you want and start reading what it did.
There is no plan to choose. Evie is MIT licensed and runs on your hardware — you only ever pay the model provider you already use.
$0forever
The whole app, on your machine.
Download for macOSYour key
Billed by them, never seen by us.
Read the setup guideEverything else is in the docs, and the parts we have not built yet are on the public roadmap.
eve is the framework the bots run on: instructions, tools, skills, and durable sessions that survive restarts. Evie is the window onto it — it starts the runtime, keeps the transcript, and gives every agent a face and a name.
Yes, and that is the deal. Evie uses whatever provider your agents are already set up for, with credentials that stay on your machine. There is no Evie account in the middle, no proxy, and no margin on your tokens.
Only what a bot sends to the model provider you picked, and to the services you connected it to. Threads, checkpoints, and keys live in your Evie home directory — there is no server of ours for them to reach.
The desktop app is macOS today. Everywhere else, `npx evie` serves the same app from any machine with Node and you open it in a browser. That is not the consolation path: it is the same one remote access uses.
Open the web app over your network, or put the machine on Tailscale and sign in from tryevie.ai. Either way the phone is a window onto the environment at home, not a second copy of it, so the thread you left open is the thread you land in.
Yes. Evie is MIT licensed and a good number of people already run forks. The roadmap and the design notes are public too, so you can see where it is going before you decide to branch.
Your team of always-on bots that you can give real work to.