Rakazo

Install the OpenQuok CLI and openquok-core skill on Rakazo bot sandboxes you self-host.

2 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Start your free trial

Prerequisites

A Rakazo deployment you control — Docker images on a laptop or VPS, or a dev stack from source.
At least one bot with its own sandbox computer (browser, shell, and persisted home).
Node.js on the bot sandbox when you install @openquok/auto-cli globally.

Official product and self-hosting docs: Rakazo self-hosting and the documentation hub.

Installation

Run Rakazo

Install with published Docker images or run from source. Sign in, connect a model, and create a bot. Open the bot computer when you need a shell.

Install the global OpenQuok CLI

On the bot sandbox terminal:

npm install -g @openquok/auto-cli@latest
openquok --version

Production auth uses the API at https://cli-auth.openquok.com and opens the browser on https://www.openquok.com/cli/device/verify.

CLI version update

Installing a skill does not change openquok --version. Run npm install -g @openquok/auto-cli@latest on the sandbox when you need a newer CLI.

Install the openquok-core skill

The skill file lives at agent/skills/openquok-core/SKILL.md in the monorepo. Register it as a bot skill on the sandbox. Choose one install path:

mkdir -p ~/skills/openquok-core
curl -fsSL "https://raw.githubusercontent.com/Ratimon/openquok-monorepo/main/agent/skills/openquok-core/SKILL.md" 
  -o ~/skills/openquok-core/SKILL.md

Register the saved file as a bot skill named openquok-core in the Rakazo UI.

Authenticate

Recommended: ask the bot to log in to OpenQuok. It runs device OAuth on its sandbox; open the link on your phone, sign in if needed, and tap Authorize.

Alternative for headless runs: rotate a programmatic token from the OpenQuok dashboard (Account → Settings → Developers → Access):

export OPENQUOK_API_KEY=opo_your_programmatic_token
openquok auth:status

Credentials stay on the bot sandbox — not in Slack or mobile chat history.

Confirm the bot can run commands

After auth, ask your bot to run:

openquok integrations:list

You should see connected channels for your workspace.

Optional MCP

You can add OpenQuok as an HTTPS MCP server under Integrations instead of or beside the CLI skill. Copy the MCP URL and token from Developers → Access on OpenQuok. CLI-first scheduling stays the default for repeatable bot routines.

Rakazo integration

Landing page for Rakazo + OpenQuok

Grok Bot

Managed xAI cloud teammates — compare when you pick a host

OpenClaw

Self-hosted messaging gateway skill install

Introduction to OpenQuok CLI

Auth, commands, and workspace concepts