Agent HQ Installation

Summary

• 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.

Setup steps

• 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

• 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.

Runtime commands

• 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

Tips

• 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.

Release notes

• 2026-02-09 – Mission-control stack created, README translated to English, changelog added, and the Clawdhub installer skill [email protected] published (now mirrored with this manifest).