Quick Start

Get RivetOS running in under 5 minutes. Two paths: Docker (recommended) or bare-metal.

Prerequisites

Requirement	Version	Check
Node.js	≥ 24	`node --version`
npm	≥ 10	`npm --version`
Git	any	`git --version`
Docker (optional)	≥ 24	`docker --version`

Note: npm install automatically builds all packages via postinstall. No separate build step needed.

Option A: Interactive Setup (Recommended)

The rivetos init wizard walks you through everything — deployment target, agent configuration, API keys, channels, and generates your config automatically.

git clone https://github.com/philbert440/rivetOS.git
cd rivetOS
npm install
npx rivetos init

The wizard will:

Detect your environment — Docker available? Proxmox? How much memory?
Choose deployment target — Docker (recommended), Proxmox, or manual
Configure agents — pick a provider, enter your API key, choose a model
Configure channels — Discord, Telegram, Voice, or API-only
Review and deploy — summary of your choices, then one-click deploy

After the wizard completes, your agent is running.

Option B: Docker (Manual)

1. Clone and install

git clone https://github.com/philbert440/rivetOS.git
cd rivetOS
npm install

2. Create your config

cp config.example.yaml config.yaml

Edit config.yaml with your settings:

runtime:
  workspace: ~/.rivetos/workspace
  default_agent: myagent

agents:
  myagent:
    provider: anthropic

providers:
  anthropic:
    model: claude-sonnet-4-20250514
    max_tokens: 8192

channels:
  discord:
    channel_bindings:
      "YOUR_CHANNEL_ID": myagent

memory:
  postgres:
    # Connection string is set via RIVETOS_PG_URL env var

3. Set up secrets

cp .env.example .env

Edit .env:

ANTHROPIC_API_KEY=sk-ant-...
DISCORD_BOT_TOKEN=...
RIVETOS_PG_URL=postgresql://rivetos:rivetos@localhost:5432/rivetos

Security: Never put API keys in config.yaml. Always use .env or environment variables.

4. Build and run with Docker

# Build container images from source
npx rivetos build

# Start everything (datahub + agent)
docker compose up -d

# Check status
npx rivetos status

# View logs
npx rivetos logs --follow

5. Verify

# Run diagnostics
npx rivetos doctor

# Run smoke tests
npx rivetos test

Option C: Bare-Metal (No Docker)

Run RivetOS directly on your machine. You’ll need PostgreSQL running separately.

1. Clone and install

git clone https://github.com/philbert440/rivetOS.git
cd rivetOS
npm install

2. Set up PostgreSQL

RivetOS needs PostgreSQL 16+ with the pgvector extension.

# Ubuntu/Debian
sudo apt install postgresql-16 postgresql-16-pgvector

# macOS (Homebrew)
brew install postgresql@16
brew install pgvector

# Create database
createdb rivetos
psql rivetos -c "CREATE EXTENSION IF NOT EXISTS vector;"

3. Create config and secrets

cp config.example.yaml config.yaml
cp .env.example .env

Edit both files as described in Option B, steps 2-3.

4. Create workspace

mkdir -p workspace/memory

Add your workspace files:

File	Purpose	Required?
`workspace/CORE.md`	Agent identity and personality	Yes
`workspace/USER.md`	Who the agent is helping	Yes
`workspace/WORKSPACE.md`	Operating rules and conventions	Yes
`workspace/MEMORY.md`	Context index for the memory system	Optional
`workspace/CAPABILITIES.md`	Extended tool/skill reference	Optional

See the Workspace Files section below for details.

5. Start

npx rivetos start

6. Install as a system service (optional)

# Install as a systemd service
npx rivetos service install

# Now it starts on boot
sudo systemctl status rivetos

Workspace Files

Workspace files are markdown documents injected into the agent’s system prompt. They define who the agent is and how it behaves.

Required Files

CORE.md — Agent identity, personality, values, and behavioral rules.

# CORE.md — Who You Are

You are a helpful AI assistant named Rivet.

## Working Style
- Be direct and concise
- Show your reasoning
- Ask before making destructive changes

USER.md — Information about the person the agent is helping.

# USER.md — About Your Human

- **Name:** Phil
- **Timezone:** America/New_York
- **Preferences:** TypeScript, Next.js, direct communication

WORKSPACE.md — Operating rules, safety boundaries, and conventions.

# WORKSPACE.md — Operating Rules

## Safety
- Don't delete files without asking
- Don't send emails without approval
- Keep secrets private

## Every Session
1. Read CORE.md, USER.md, WORKSPACE.md
2. Check recent memory files
3. Get to work

Optional Files

MEMORY.md — A lightweight index into the memory system. The agent uses this to know what to search for.

CAPABILITIES.md — Extended reference for tools, skills, and infrastructure. Included in the system prompt for local models where token cost isn’t a concern.

HEARTBEAT.md — Instructions for periodic background tasks. Only injected during heartbeat turns, not regular conversation.

memory/YYYY-MM-DD.md — Daily notes. The agent reads recent daily notes for context continuity between sessions.

First Conversation

Once your agent is running, talk to it through your configured channel:

Discord: Send a message in the bound channel. Terminal: npx rivetos chat myagent "Hello, who are you?" API: curl -X POST http://localhost:3100/api/message -H 'Content-Type: application/json' -d '{"content": "Hello"}'

Useful Commands

In any channel, you can use slash commands:

Command	What it does
`/stop`	Abort the current response immediately
`/new`	Start a fresh session (clears conversation history)
`/status`	Show agent status and runtime info
`/model`	Show or switch the current model
`/think [level]`	Set thinking depth: off, low, medium, high
`/steer [message]`	Inject context mid-response
`/context add [file]`	Pin a file into the agent’s context
`/context list`	Show pinned files
`/context clear`	Remove all pinned files

CLI Reference (Quick)

rivetos init              # Interactive setup wizard
rivetos start             # Start the runtime
rivetos stop              # Stop the running instance
rivetos status            # Show runtime status and metrics
rivetos doctor            # Health check (config, connectivity, containers)
rivetos test              # Smoke test (provider, memory, tools)
rivetos logs              # Tail agent logs
rivetos update            # Pull latest source, rebuild, restart
rivetos config            # View or edit configuration
rivetos agent add         # Add a new agent
rivetos agent list        # List configured agents
rivetos mesh list         # Show mesh peers (multi-instance)
rivetos mesh ping         # Health check all peers
rivetos build             # Build container images from source
rivetos infra up          # Deploy infrastructure from config
rivetos infra preview     # Preview infrastructure changes
rivetos infra destroy     # Tear down infrastructure
rivetos service install   # Install as systemd service
rivetos plugins list      # Show loaded plugins
rivetos skills list       # Show available skills

Next Steps

Channel Setup — Connect to Discord, Telegram, voice, and agent-to-agent messaging
Provider Setup — Configure Anthropic, xAI, Google, Ollama, and llama-server providers
Configuration Reference — Every config option explained
Architecture — How the system works
Plugins — How to write your own channel, provider, or tool
Skills — How to write and share skills
Deployment — Docker, Proxmox, multi-agent, networking
Troubleshooting — Common issues and fixes

Quick Troubleshooting

Agent doesn’t respond?

Run npx rivetos doctor to check connectivity
Check npx rivetos logs for errors
Verify your API key is set in .env

Docker containers won’t start?

Run docker compose logs datahub to check PostgreSQL
Ensure port 5432 isn’t already in use
Try npx rivetos build to rebuild images

Memory search returns nothing?

Check PostgreSQL connection: npx rivetos test --quick
Embeddings may still be processing — check npx rivetos status for queue depth

Can’t find config?

Default location: ./config.yaml or ~/.rivetos/config.yaml
Override with: npx rivetos start --config /path/to/config.yaml