ClawBridge is a GitHub-hosted AI wrapper for OpenClaw that simplifies installation, verification, provider setup, and first-run onboarding for beginners and non-coders.
It wraps the official OpenClaw installation flow with a guided local UI + API verification experience.
ClawBridge is currently a web UI + local API MVP.
Today it runs as:
- a React + Vite frontend
- a local Express + TypeScript backend
It is not yet a packaged Electron desktop app. Full desktop packaging is planned in a later phase.
OpenClaw is powerful, but many users still struggle with:
- Node.js and Git prerequisites
- shell / PATH issues
- verifying whether OpenClaw is installed
- provider and API key setup
- doctor / health-check flows
- first-run troubleshooting
- terminal fear for non-coders
ClawBridge solves this by acting as a local onboarding assistant and installation wrapper.
- launch test agent preflight workflow
- React + Vite frontend UI
- local Express + TypeScript backend API
- machine system checks
- OS / architecture / shell detection
- Node.js version detection
- Git version detection
- OpenClaw installation detection
- recommended install command generation
- guided next-step onboarding
- OpenAI provider support
- Anthropic provider support
- Ollama provider support
- local/custom provider support
- latest recommended model selection
- custom model input support
- provider-specific env generation
- OpenClaw version verification
- OpenClaw status checks
- gateway status verification
- channels status probing
- deep status verification
- OpenClaw doctor execution
- local
.env.clawbridgegeneration - gitignored local secret storage
- local-only generated provider configs
- first-run launch orchestration
- provider reachability testing
- structured activity logs
- richer diagnostics and troubleshooting UX
- componentized frontend architecture
- premium control-center UI
- Electron desktop packaging
- provider failover and routing
- agent observability
- OpenTelemetry integration
- Docker + Kubernetes support
- secure secrets storage
- plugin architecture
- AI-assisted operational workflows
The real friction in AI tools is rarely the model.
The hardest parts are:
- local environment setup
- PATH problems
- provider confusion
- shell errors
- onboarding friction
- verification steps
ClawBridge is evolving toward an operational UX layer for AI agents — focused on onboarding, diagnostics, provider orchestration, reliability, and developer experience for modern AI systems.
Frontend (React + Vite)
↓
Local API (Express + TypeScript)
↓
Machine inspection
↓
OpenClaw verification
↓
Provider orchestration
↓
Operational diagnostics
clawbridge/
├── apps/
│ └── desktop/ # React + Vite frontend
├── packages/
│ └── core/ # Local API + system checks
├── docs/ # Architecture, security, providers, roadmap
├── scripts/ # Install/helper scripts
├── templates/ # Provider/env templates
├── .nvmrc # Node 24 pin
├── package.json
└── pnpm-workspace.yaml
- Node.js 24
- pnpm 10+
- Git
- macOS / Linux / Windows
- git clone https://github.com/MahendraRao/clawbridge.git
- cd clawbridge
Use the correct Node version
- nvm use
If Node 24 is not installed:
- nvm install 24
- nvm use 24
Enable Corepack
- corepack enable
Install dependencies
- pnpm install
Start the project
- pnpm dev
-
frontend → http://localhost:5173
-
backend API → http://localhost:8787
-
open ClawBridge UI
-
click Run system check
-
detect:
- OS
- architecture
- shell
- Node.js
- Git
- OpenClaw
-
verify OpenClaw installation state
-
generate provider-specific configuration
-
select:
- OpenAI
- Anthropic
- Ollama
- local/custom models
-
generate local
.env.clawbridge -
run verification commands:
- Version
- Status
- Gateway
- Channels
- Deep Status
- Doctor
-
guide the user toward next operational steps
- OS: darwin
- Architecture: arm64
- Shell: /bin/zsh
- Node.js: Installed (v24.1.0)
- Git: Installed (git version 2.x)
- OpenClaw: Installed (2026.x.x)
- gateway status: reachable
- channels probe: successful
- doctor: completed
- curl -fsSL https://openclaw.ai/install.sh | bash
Recommended screenshots:
- homepage before system check
- machine summary after check
- OpenClaw missing state
- OpenClaw Installed state
- Test Agent
- frontend scaffold
- backend local API
- system checks
- Node/Git/OpenClaw detection
- install command recommendation
- OpenAI support
- Anthropic support
- Ollama support
- local/custom models
- provider-specific env generation
- secure local config storage
- launch orchestration
- provider reachability testing
- structured logs
- activity history
- richer diagnostics
- troubleshooting workflows
- session visibility
- execution tracing
- provider health metrics
- token usage visibility
- agent observability
- Docker integration
- Kubernetes integration
- OpenTelemetry support
- gateway health probes
- deployment diagnostics
- plugin architecture
- packaged desktop app
- SDK extraction
- AI-assisted operational workflows
- never commit .env
- never log raw API keys
- prefer OS-native secret stores
- review shell execution carefully
- avoid blind auto-run flows until hardened mode is added
Generated provider configs are stored locally inside:
generated/.env.clawbridgeThese files are gitignored by default and are not committed to the repository.
Never commit real API keys or credentials. Rotate exposed credentials immediately if accidentally shared.
Issue as -> pnpm: command not found
- nvm use 24
- npm install -g pnpm
## 🧩 Environment consistency notes
This repo is pinned to:
- Node 24 via `.nvmrc`
- pnpm 10 via `packageManager`
## If commands fail after entering the project directory, run:
* nvm use
* corepack enable
* pnpm -v
Then continue with:
* pnpm install
* pnpm dev-
Use:
| curl -fsSL https://openclaw.ai/install.sh | bash
-
Verify:
- which openclaw
- echo $PATH
Contributions are welcome.
Good areas to contribute:
- provider integrations
- Windows support
- Electron packaging
- improved diagnostics
- secure credential storage
- UI/UX improvements