Everything you need to run your Rick. Installation, commands, configuration, troubleshooting—it's all here.
Public self-service execution is paused while signed distribution contracts are verified. Run the browser preflight now; the published installer script exits before mutation.
The command above currently returns the paused-release notice without changing the machine. Review status and source on the canonical install page.
After install, Rick sends a heartbeat to confirm he's alive. You'll see a RICK_ONLINE message in your Telegram (if configured) and in the terminal. This is Rick's way of saying "I'm ready." From here, Rick begins his boot sequence: loading your SOUL.md, scanning for pending tasks, and running an initial environment audit.
All Rick operations run through the rick CLI. Here's every command you need.
Rick supports multiple LLM providers. Configure one or many—Rick will route to the best available model for each task.
The default and recommended provider. Haiku (Free), Sonnet (Pro), or Opus (Business) depending on your tier.
Get your key from:
console.anthropic.comKey format: sk-ant-...
Used as a fallback model on Pro and Business tiers. Supports GPT-4o and later models.
Get your key from:
platform.openai.comKey format: sk-...
Available as an additional fallback. Gemini Pro and Ultra supported on Pro+ tiers.
Get your key from:
aistudio.google.comKey format: AIza...
Run models locally for free. No API key needed. Great for experimentation and privacy-sensitive tasks.
Install from:
ollama.aiRuns on localhost:11434
All API keys are stored locally in your workspace config at ~/.openclaw/workspace. Keys never leave your machine. You can set them during install, or update them later with rick config.
Telegram is Rick's native communication channel. Here's how to set it up in 5 steps.
Open Telegram, search for @BotFather, and send /newbot. Follow the prompts to name your bot (e.g., "My Rick Bot").
BotFather will give you a token like 7123456789:AAH.... Copy this—you'll need it in the next step.
Paste the token during rick setup, or add it later via rick config. Rick stores it locally in your workspace.
Message @userinfobot on Telegram. It will reply with your numeric chat ID. Enter this during setup so Rick knows where to send messages.
Run rick start and send any message to your bot. Rick should respond within seconds. If he does—you're live.
Rick comes in three tiers. Start free, upgrade when you need more power.
| Feature | Free | Pro — $29/mo | Business — $499/mo |
|---|---|---|---|
| Skills | 5 | 16 | 24 |
| Models | Haiku | Sonnet + 3 fallbacks | Opus + 5 fallbacks |
| Channels | Telegram | + Slack | + Email + Webhooks |
| Briefings | — | Daily + Weekly | + Nightly + Monthly Strategy |
| Sub-agents | No | No | Yes (5 concurrent) |
| Overnight | No | No | Graduated autonomy |
| Strategy Panel | No | No | Multi-model consensus |
| Rick Network | Rank only | + Benchmarks + Tips | + Prime channel |
See full pricing details at /pro.
Rick works without network participation. Passing --telemetry explicitly opts an installation into the Rick network under the disclosed privacy terms.
Task counts, skill usage patterns, and performance stats. No private data, no conversation content, no file contents. Ever.
Pro and Business users get comparative insights: "You completed more tasks than 87% of Ricks" or "Your content skill is in the top 10%." Real data, not vanity metrics.
Business-tier Ricks receive network-wide intelligence in their strategy reviews—trending patterns, emerging best practices, and aggregate performance data.
Network participation is off by default. Keep the default or pass --no-telemetry explicitly:
Rick will still work perfectly. You just won't see benchmarks or network insights.
The public updater contract is paused and unverified. The items below are release requirements, not currently available behavior.
Most problems have a one-line fix. Click to expand.
Run the health check locally. Before sharing anything, remove API keys, tokens, emails, usernames, IP addresses, and home-directory paths:
Share only the redacted failed check with @rickaiassistant_bot or use the local error resolver.
First, try a restart:
If that does not work, run rick doctor, redact its failed check, and use the install error resolver.
The current public repair.sh is a release-status probe only: it exits 78, sends no network request, and changes no files.
The public self-hosted release and updater contract are paused. Do not run an assumed update command or trust an automatic schedule.
Inspect the installed version with the read-only check above, then request a signed, version-specific recovery path from support.
Generate a connection code so Rick HQ can diagnose your instance remotely:
Share the code with @rickaiassistant_bot only if your existing installation documents what the code grants. Response timing is not guaranteed.
Inspect which process is holding port 18789 before deciding whether anything should stop:
Stop a process only after identifying it and confirming it is safe to stop. Prefer that service's own stop command, then run rick doctor again.
The current public repair script cannot re-establish or register a network connection. It is a fail-closed status probe while release contracts are paused.
Existing verified customers should run rick doctor, inspect the exact failed network check, and request manual support with a redacted result.
The public installer is paused and exits before changing a machine. Do not use it as a reinstall path.
Existing verified customers should back up their workspace and request the exact signed version-specific recovery procedure from support.
Pass the uninstall flag to the installer:
This removes the Rick runtime and its scheduled services, but preserves your configuration, workspace, and memory under ~/.openclaw/ so you can inspect, back up, or reuse them later.
Check the key format for your provider:
Make sure you copied the full key with no trailing spaces. Update it with rick config and then rick restart.
Stuck? Reach out. We respond to everything.