AI Commander Dashboard

A companion dashboard for AI Commander agents. Displays inbound emails collected by the email-webhook skill and shows the status of browser sessions created by the browser-auth skill.

This skill is a read-only viewer — it does not capture credentials, control browsers, or send messages. It simply reads local data files and serves them via a token-protected web UI.

Companion Skills

Skill	What it does
email-webhook	Receives inbound emails and writes them to inbox.jsonl
browser-auth	Runs a remote browser tunnel and writes session data to session.json

This dashboard reads both files and displays them in one place.

What This Skill Does

• Reads inbox.jsonl and displays the last 50 inbound emails
• Reads session.json and shows whether an active browser session exists
• Serves a token-gated web UI on a configurable local port
• Refreshes automatically every 5 seconds

Environment Variables

Variable	Required	Default	Description
DASHBOARD_TOKEN	Yes	—	Secret token for accessing the dashboard.
PORT	No	19195	Port for the web dashboard.
DASHBOARD_HOST	No	127.0.0.1	IP to bind the dashboard to.
INBOX_PATH	No	./data/inbox.jsonl	Path to inbound email data (from email-webhook).
SESSION_PATH	No	./data/session.json	Path to session file (from browser-auth).

Setup

1. Install dependencies:

   npm install express@4.21.2
   

2. Start (zero config needed):

   node scripts/server.js
   

3. Read the printed URL — it includes the auto-generated token:

   🏠 AI COMMANDER DASHBOARD READY
   Access URL: http://YOUR_IP:19195/?token=a3f9c2...
   

That's it. No configuration required.

Optional Environment Variables

Override defaults only if needed:

Variable	Default	Description
DASHBOARD_TOKEN	(random)	Custom token instead of auto-generated
PORT	19195	Server port
DASHBOARD_HOST	0.0.0.0	Bind address
INBOX_PATH	./data/inbox.jsonl	Path to email data (from email-webhook)
SESSION_PATH	./data/session.json	Path to session file (from browser-auth)

Security

• A fresh random token is generated on every start if DASHBOARD_TOKEN is not set
• All requests require the token (?token=, X-Dashboard-Token header, or Authorization: Bearer)
• The UI stores the token in localStorage and removes it from the URL after load