Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Deploy the Agent HQ mission-control stack (Express + React + Telegram notifier / Jarvis summary) so other Clawdbot teams can spin up the same board, high-priority watcher, and alert automation. Includes setup, telemetry, and automation hooks.
Deploy the Agent HQ mission-control stack (Express + React + Telegram notifier / Jarvis summary) so other Clawdbot teams can spin up the same board, high-priority watcher, and alert automation. Includes setup, telemetry, and automation hooks.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Backend + frontend: Express API with SQLite board + Vite/React UI served from frontend-react/dist. Automation pieces: Jarvis summary (scripts/jarvis-connector.js), Telegram notifier (scripts/notify-jarvis-telegram.js + cron), plus a high-priority watcher inside backend/server.js. Data: data/board.json seeds missions/agents/cards; the board persists in data/mission.db. Notifications: config/telegram.json (or AGENT_HQ_TELEGRAM_* env vars) lets you send alerts to Telegram.
Clone the repo and install deps: git clone https://github.com/thibautrey/agent-hq.git cd agent-hq npm install npm --prefix frontend-react install Edit config/telegram.json with your botToken/chatId (or set AGENT_HQ_TELEGRAM_TOKEN/AGENT_HQ_TELEGRAM_CHAT_ID). Keep this file secret. Build the UI and start the server: npm --prefix frontend-react run build npm run start:agent-hq The UI is served on / and the API lives under /api (default port 4000). Configure cron jobs (Heartbeats + Telegram): Jarvis summary: node scripts/jarvis-connector.js or scripts/notify-jarvis-telegram.js --force as needed. Telegram notifier cron (see run-telegram-notifier.sh). Use the UI to create cards or POST /api/cards//api/cards/quick to keep Jarvis busy.
View board: curl http://localhost:4000/api/board Trigger Telegram alert: curl -X POST http://localhost:4000/api/notify-telegram Quick card: curl -X POST http://localhost:4000/api/cards/quick -H "Content-Type: application/json" -d '{"text":"Design review needed"}' Jarvis summary: node scripts/jarvis-connector.js
Drop cards directly into data/board.json before first run for a seeded mission. high_priority_jobs table in SQLite prevents duplicate Telegram alerts. AGENT_HQ_API_TOKEN protects mutating endpoints for scripted integrations.
2026-02-09 β Mission-control stack created, README translated to English, changelog added, and the Clawdhub installer skill agent-hq@1.0.0 published (now mirrored with this manifest). Enjoy running your own Mission Control.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.