ClawPanel is a comprehensive web dashboard and control center for managing OpenClaw AI instances. Unlike standard cloud-based panels, ClawPanel runs entirely locally (or on your VPS) to hook directly into your OpenClaw filesystem and CLI interfaces, offering zero-latency monitoring, configuration, and project administration.
ClawPanel is built as a complete interface over the openclaw daemon architecture, bringing terminal-based features directly to a graphical UI:
- Agents Manager: Agents are fully operational — create new agents, set their identities, and choose which skills they're allowed to use. Read and edit core workspace instructions seamlessly.
- File Manager: Comprehensive workspace file management supporting bulk deletion via checkboxes and multi-column sorting (Name, Size, Date) across both Tree and List views.
- Channels Monitoring: Perform live network health checks for your running agents across platforms (Telegram, Discord, User APIs, etc.).
- Skills Explorer: Interface directly with OpenClaw's CLI plugin registry. Enable/disable default skills or explore external skill implementations securely from your own VPS.
- Cron Jobs Management: Visual oversight of background chronologically-scheduled operations spanning the active agents.
- Kanban Project Tracker: An integrated project management suite to overview ongoing AI workloads ranging from 'Review' queues to fully 'Completed' multi-agent automation runs.
- Email Automation: Monitor local email processing and queue integration logic without maintaining separate dedicated webhooks.
- Framework: Next.js 15 (App Router)
- Styling: Tailwind CSS +
lucide-react - Architecture: CLI & Filesystem-First design
- File management endpoints interact directly with
openclawvia child process invocations (e.g.,openclaw agents list --json) avoiding unreliable WebSockets.
- File management endpoints interact directly with
- Authentication: Firebase Client/Admin Auth
On your primary device or VPS, ClawPanel relies on several environment configs to properly link to the OpenClaw environment.
You must define a .env.local file at the root of the project:
# Path to the active openclaw global or system binary
OPENCLAW_BIN=openclaw
# Fallback path to the primary agent's workspace directory
WORKSPACE_PATH=/home/clawdbot/clawd
# Client-Side Firebase configuration
NEXT_PUBLIC_FIREBASE_API_KEY=your_api_key
NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=your_project.firebaseapp.com
NEXT_PUBLIC_FIREBASE_PROJECT_ID=your_project_id
NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET=your_bucket
NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID=your_sender_id
NEXT_PUBLIC_FIREBASE_APP_ID=your_app_idTo get started with local development or deploying:
-
Clone and install dependencies:
npm install
-
Run the automated configuration setup wizard to link ClawPanel to your
openclawinstallation path and active workspace:npm run setup
-
Start the development server:
npm run dev
Note: Development features requiring the
openclawCLI will expectopenclawto be globally installed (npm i -g openclaw@latest) and authenticated on the same machine.
ClawPanel is designed to be built and run on the same VPS environment that typically runs the openclaw gateway process.
To deploy:
- Build the optimal production payload:
npm run build- Run utilizing
pm2for process persistence:
pm2 start npm --name "clawpanel" -- run start