Quickstart
Quickstart (CLI)
Stand up your first ROAM team from the command line in under 10 minutes. You will install ROAM, run the setup wizard, define a team, connect a harness, and watch a signed handoff land in the file system.
What you need
- macOS, Linux, or Windows.
- One of: Claude Code, Cursor, ChatGPT, Gemini, n8n, or any local model.
- A terminal. That is it.
1. Install
Use the CLI path when you want to try ROAM from a terminal. It installs the roam command globally.
npm install -g @veritera.ai/roamVerify:
roam --help2. Initialize a workspace
roam init starts the setup wizard and writes the workspace to ~/ROAM/<session-name>/ by default. Use an explicit path if you want to place it somewhere else.
roam init my-team
cd ~/ROAM/my-teamThe wizard starts with the way you work, then creates the local operating model around that.
- Leadership topology: Chief of staff, Hands-on captain, Peer mesh, or Not sure.
- Harnesses: choose from the verified harnesses your tier allows.
- Project template: Investor deliverable, Software build, Research, Marketing, or Custom.
- Runtime mode: Always-on or Work-hours.
- Adoption: auto-scan common directories or use
roam adoptfor explicit paths. - Trust settings: approval gates, notification behavior, and EYDII watch. EYDII itself is always on.
You will see a new directory laid out with the canonical ROAM structure: roles/, memory/, events/, signed/. Read it. It is yours.
ROAM does not require a Veritera account or email to run locally. The harnesses you connect keep using the credentials and providers you chose.
3. Review your team
Open roles/. Each role is a markdown file with a name, a job description, and a model preference. Edit them like any other file.
# roles/ceo.md
Name: Operator
Harness: Telegram
Job: Decide priorities. Approve handoffs. Never write code.
# roles/eng.md
Name: ENG
Harness: Claude Code
Job: Implement approved work. Run tests. Report drift or blockers.4. Run it
roam daemon start
roam dashboard --watchStart the daemon when you are ready to run the workspace. ROAM picks up the team from roles/, wires each role to its harness, and waits for work. Drop a task into events/inbox/ or send a message from the operator harness if you enabled Telegram or Discord.
5. Watch a handoff
When the operator sends a task, ROAM routes it to the right role and records the handoff. Open signed/ in another terminal:
tail -f signed/*.jsonConsequential actions are written to disk with EYDII evidence. You can inspect the handoff yourself before you grant more autonomy.
Next
- Connect another harness — add Cursor, ChatGPT, Gemini, or a local model.
- Read the EYDII concept — understand what is watching every handoff and why.
- CLI reference — every command and flag.