Start here
Vyre docs
Vyre is the agentic command center for AI-native teams. Our mission is to help every professional services team become AI-native.
In an AI-native team, people set the direction and make the calls, and agents do the work: they draft, track, follow up and keep every job moving. Vyre gives both one place to work together, on servers the team owns, where anything that leaves the team waits for a person's yes.
People and agents share chats, records, files, a vault, Flows and projects. Any model works on your own accounts. Start with the architecture overview for the picture, or the full statement in the spec.
Start here
The fastest path, in order:
- Install: put Vyre on a Linux server and your Mac. From the Mac it is one command.
- Your first day: open Lumen, start a thread in a project, launch an agent, store a secret, find something from last week.
On a Mac, the install starts here:
npm install -g https://vyre.run/box/vyre.tgz
vyre up
Vyre is not on npm yet, so the package comes from vyre.run. vyre up asks where Vyre should run; pick a server and give it the address you SSH to (for example [email protected]). If something stops you, see Troubleshooting. No Docker on the server? See Without Docker.
Who each section is for
| Section | For | What is in it |
|---|---|---|
| Get started | users | Install, onboarding, the first day, fixes for common failures. |
| Using Vyre | users | One page per surface and feature: Lumen, the Vyre app, Chat, the CLI, projects and threads, agents, the vault, memory, watchers, connectors, your private network, the phone, looking after the box. |
| Concepts | users, builders | The ideas the rest leans on: the box and the Mac, your private network, presence, the security floor, modules. |
| Build on Vyre | builders, agents | The module contract, tools and events, writing a module, the MCP hub. |
| Reference | everyone | Generated from the code: every command, tool, event, config key and module. |
| Architecture | builders, operators | Layers, surfaces, the repository, the spec, performance, and the decision records. |
| Security | operators, builders | The floor, how the vault seals values, who can reach the box, container hardening, how to report a problem. |
| Contributing | builders | Repository layout, engineering rules, tests, and how to write these docs. |
| Changelog | everyone | What changed, newest first. |
For agents
Every page on this site is also served as its Markdown source at the same path with .md on the end. https://docs.vyre.run/using/vault is the rendered page, and https://docs.vyre.run/using/vault.md is its source, front matter included.
Two more files follow the llms.txt convention:
- /llms.txt: an index of every page, by section, each with its
.mdlink and one-line summary. - /llms-full.txt: every page's Markdown in nav order, in one file.
Each page's front matter says who it is for (audience) and whether it is shipped (status: stable), partly shipped (draft) or not built yet (planned). Treat a planned page as a description of intent, not of the code. The contract behind all of this is in Writing the docs.