Development build and run
Distinguish server development, desktop packaging and UI fixtures.
Get the source
git clone https://github.com/acosmi/OpenMyBot.git
cd OpenMyBotgit clone https://github.com/acosmi/OpenMyBot.git
cd OpenMyBotUse the pinned toolchain, Cargo.lock and platform dependencies. An old source snapshot is not the current feature baseline.
Server entry
cargo build --release -p openbot-server --bin wrok-bot-server
./target/release/wrok-bot-server --helpcargo build --release -p openbot-server --bin wrok-bot-server
./target/release/wrok-bot-server --helpSet WROK_BOT_DATABASE_URL and WROK_BOT_KEY_ENCRYPTION_KEY securely. Set WROK_BOT_APP_DIST_DIR to the matching compiled workbench when serving the UI.
./target/release/wrok-bot-server --local./target/release/wrok-bot-server --localLocal mode selects the first-party single-user workspace. Database schema, keys and frontend must match the build. Read startup failures rather than deleting keys or bypassing checks.
Build the workbench frontend
The Rust/WASM frontend is in crates/wrokbot-ui. From the repository root, install the pinned build tools and build the matching assets:
rustup target add wasm32-unknown-unknown
cargo fetch --locked
cargo xtask tools fetch
cargo xtask tools verify
WROK_BOT_TOOLS_DIR="$(pwd)/target/tools/bin"
cd crates/wrokbot-ui
PATH="$WROK_BOT_TOOLS_DIR:$PATH" trunk build --release --offline --locked
cd ../..
export WROK_BOT_APP_DIST_DIR="$(pwd)/crates/wrokbot-ui/dist"rustup target add wasm32-unknown-unknown
cargo fetch --locked
cargo xtask tools fetch
cargo xtask tools verify
WROK_BOT_TOOLS_DIR="$(pwd)/target/tools/bin"
cd crates/wrokbot-ui
PATH="$WROK_BOT_TOOLS_DIR:$PATH" trunk build --release --offline --locked
cd ../..
export WROK_BOT_APP_DIST_DIR="$(pwd)/crates/wrokbot-ui/dist"Start the server in this terminal as described above. Initial dependency downloads require network access; the Trunk build uses the locked tool versions offline. Keep the server, frontend and configuration on the same source revision.
Desktop assembly
The desktop uses openbot-desktop with desktop-launcher and the wrok-bot binary. Startup also requires matching release metadata, PostgreSQL resources, host permissions and packaging identity. A cargo build is not a complete desktop installer.
There is no public Release. Follow a specific internal candidate's instructions when one is provided; UI fixtures and web previews are not a real local-data environment.
First checks
Confirm account/workspace, language, connection and model catalog. Try a low-impact task and verify responses, tool results, Stop and history recovery separately. macOS signed-app acceptance is still incomplete; Windows, Linux and mobile support are independently verified.