Docs
Refer a friend. Get a weekly-quota reset.Friend signs up and uses it → +1 reset (valid 30 days) · up to 10% cash back on their spend.
+1 resetGenerate link

Build, initialize and start

Prepare dependencies and start the foreground daemon with an explicit data directory.

Prerequisites

Use the repository's pinned Rust toolchain. Provide an absolute directory containing PostgreSQL 17's postgres and initdb. Shared server dependencies also require xmlsec1, libxml2 and OpenSSL. This is the macOS-oriented developer entry point, not a verified Windows installer.

bash
git clone https://github.com/acosmi/OpenMyBot.git
cd OpenMyBot
cargo build --release -p omb-cli -p omb-channels
git clone https://github.com/acosmi/OpenMyBot.git
cd OpenMyBot
cargo build --release -p omb-cli -p omb-channels

Do not use --all-features: it enables test-only channel parameters. Put the binaries on the host process's actual PATH. Built-in channel installation expects the plugin binaries beside openmybot.

Initialize

Replace the example binary path with your own absolute path:

bash
export OPENMYBOT_DATA_DIR="$HOME/Library/Application Support/OpenMyBot"
openmybot init --pg-bin-dir /absolute/path/to/postgresql17/bin
export OPENMYBOT_DATA_DIR="$HOME/Library/Application Support/OpenMyBot"
openmybot init --pg-bin-dir /absolute/path/to/postgresql17/bin

Initialization creates a private PostgreSQL cluster and a random local key. Directory priority is --data-dir, OPENMYBOT_DATA_DIR, then $HOME/Library/Application Support/OpenMyBot. Do not share wrok Bot's data directory.

Run and inspect

Start openmybot daemon in a terminal. It stays in the foreground and supervises PostgreSQL. From another terminal run:

bash
openmybot status --json
openmybot status --json

Check process, database, deployment, authentication and plugin states. A running daemon does not establish model, channel or MCP compatibility.

Stop and restart

Use Ctrl+C, SIGINT or SIGTERM and wait for shutdown before restarting. OpenMyBot does not install an automatic background service.

The CLI, daemon, host and MCP server must use the same user and data directory. Check both when the daemon cannot be found; see troubleshooting.