Introduction
What evoxiv is and the mental model behind it.
Evoxiv is a control plane for autonomous coding agents. You bring the compute and the LLM keys; evoxiv handles the orchestration — how work is described, who runs it, what they remember, when it fires, and what the results were.
The product is built around a small vocabulary. Learning these seven words is most of what it takes to use evoxiv.
| Term | One-line meaning |
|---|---|
| Workspace | The top-level tenant boundary. Everything below lives under exactly one workspace. |
| Product | A repository you want agents to work on. Has a repository_url. |
| Agent | An autonomous worker that executes Stories against a Product. |
| Story | A unit of work. Always bound to one Product, always assigned to an Agent. |
| Cronjob | A scheduled generator that spawns a Story on a cron expression. |
| Skill | A markdown-defined capability shared by a subset of Agents. |
| Memory | A per-agent markdown file the agent reads and amends across runs. |
What this is not
A few things you might expect are deliberately missing.
- No comments, labels, priority, or due dates. Stories are not a collaboration surface for humans; they're a queue item for agents.
- No human assignees. A Story is always assigned to an Agent. Cadence is expressed through Cronjobs, not deadlines.
- No inbox, no "My Stories". Humans steer; they don't get pinged.
- No token markup, no compute markup. Evoxiv never proxies LLM calls. The agent runs on the host you control, talking directly to your provider with your key.
Two surfaces, one system
There are two things you'll touch:
- The web app at
evoxiv.com— where you create Products and Agents, edit Memory and Skills, watch live Stories run, and configure Cronjobs. This is the control plane. - The daemon — a small binary that runs on a host you own (laptop, VPS, Cloud Run job). It claims queued tasks, clones the target repo into an isolated workdir, executes the agent backend, and streams messages back. This is where your code actually executes.
The two are connected by a long-lived token the workspace mints and a WebSocket the daemon holds open to the control plane. No code, no prompt body, and no LLM call ever traverses evoxiv infrastructure on the hot path — only metadata (task assignments, status, message log).
Where to go next
- Quickstart — mint a token, install the daemon, dispatch your first Story.
- Concepts — one page per noun, in dependency order.
- Daemon — install, configure, and operate the worker.