Agent Dash
A self-hosted push inbox for AI agents that enables agents to send updates and ask questions, waiting for user answers before continuing.
README
Agent Dash
Your agents report here. A self-hosted push inbox for AI agents β deploy your own on Cloudflare's free plan, and any agent (Claude Code, Codex, Cursor, Antigravity, Kimi, or a raw ChatGPT/Claude chat) can send updates to your phone and ask you a question and wait for your answer before continuing.
Think "ntfy for agents, with a reply button." Vendor-neutral, single-user, free to run.
<p align="center"><img src="public/icon.svg" width="96" alt="Agent Dash"></p>
Why
Every AI vendor has a companion app β but it only talks to their agent. When you kick off a long research run, a refactor, or a build in Claude Code / Codex / Cursor, you either babysit the terminal or miss the moment it finishes or gets stuck.
Agent Dash is one inbox for all of them:
- π Push updates β milestones and completions land as notifications on your phone (installable PWA, works on iOS + Android).
- β Ask-and-wait β an agent can post a question (a choice, or a whole form) and poll until you answer, then continue. "I finished the research β VC or customer framing for the deck?" β you tap β it keeps going.
- π§± Structured messages β agents send typed blocks (markdown, progress bars, tables, forms), not raw text. Rendered safely, never as HTML.
- π Connect anything β a portable skill, a one-line MCP server, an OpenAPI spec for ChatGPT Actions, and drop-in Claude Code hooks.
- π Free to host β one Cloudflare Worker + D1 + KV. No Durable Objects, no Postgres, no Firebase. Fits comfortably in the free tier for one person.
Deploy your own (β5 minutes)
You need a free Cloudflare account and Node 20+.
git clone https://github.com/Prajeevan/agent-dash.git
cd agent-dash
pnpm install # or npm install
npx wrangler login # authorize wrangler with your Cloudflare account
# Create the database + KV, then wire their ids into wrangler.jsonc:
npx wrangler d1 create agent-dash
npx wrangler kv namespace create SESSIONS
# β paste the printed database_id and id into wrangler.jsonc
pnpm setup # generates keys, sets secrets, migrates DB, deploys
pnpm setup prints your worker URL, a magic login link, and your
agent connection snippet. Then:
- Scan the QR code it prints with your phone (or open the link) β Add to Home Screen β open the app β Settings β Enable notifications.
- Give an agent the MCP snippet or the skill.
Re-run pnpm run login any time for a fresh 15-minute login link + QR (rendered
locally in your terminal β the magic-link token never leaves your machine). Re-run
pnpm setup --rotate to regenerate all keys.
Connect an agent
MCP (Claude Code, Cursor, Codex, any MCP client) β one entry:
{
"mcpServers": {
"agent-dash": {
"url": "https://agent-dash.your-name.workers.dev/mcp",
"headers": { "Authorization": "Bearer YOUR_AGENT_KEY" }
}
}
}
Tools: notify(title, blocks?, priority?), ask(title, blocks), wait_for_answer(question_id).
Skill β install it into any Agent-Skills runtime (Claude Code, Cursor, Codex, β¦) straight from GitHub:
npx skills add Prajeevan/agent-dash
This drops skills/agent-dash/SKILL.md into your agent so it knows how to reach
your hub; then give it your URL + AGENT_KEY.
curl (anything that can make an HTTP request, including a raw chat) β the one-liner:
curl -X POST "$AGENT_DASH_URL/api/v1/events" \
-H "Authorization: Bearer $AGENT_KEY" -H "Content-Type: application/json" \
-d '{"agent":"claude","title":"Build finished","priority":1}'
CLI β npx agentdash connects an agent, logs you in on your phone
(QR), and sends updates/questions from scripts:
npx agentdash login # save + verify your hub URL and agent key
npx agentdash connect # write ./.mcp.json for your agent
npx agentdash notify "Build finished" --priority 1 --project "API"
ChatGPT Actions β import https://your-url/api/v1/openapi.json.
Claude Code hooks β drop-in start/finish/needs-input pushes.
How it works
Agents ββPOST /api/v1/eventsββββββΆ Cloudflare Worker (TanStack Start SSR + API)
ββPOST /api/v1/questionsβββΆ ββ /api/v1/* agent REST (bearer AGENT_KEY)
ββGET /api/v1/questions/:id ββ /mcp stateless MCP
ββ /app dashboard PWA (magic-link session)
You (PWA) βββ Web Push (VAPID) βββ ββ Bindings: D1 (events/questions/subs), KV (sessions)
ββpoll feed while openββΆ Cron: expire questions + prune old events
- No Durable Objects. Delivery is Web Push (real-time, free) plus polling β agents check for answers every ~10s; the dashboard polls a cursor feed only while a tab is open. A single-user workload stays well inside free limits.
- Two credentials, separate concerns.
AGENT_KEY(agents post/poll) andAPP_SECRET(signs your magic-login links + sessions). They rotate independently. Sessions live in KV with a TTL; "log out everywhere" bumps an epoch that invalidates them all. - Blocks, not HTML. Agent messages are
zod-validated typed blocks; the UI renders a known set β no agent-supplied markup is ever executed.
See PLAN.md for the full design rationale.
Tech
TanStack Start (React 19) on Cloudflare Workers Β· D1 Β· KV Β· Web Push (hand-rolled VAPID + RFC 8291 on WebCrypto, no Node deps) Β· Vite Β· TypeScript.
Dev: pnpm dev. Typecheck: pnpm typecheck. Deploy: pnpm run deploy.
Instant mode (optional)
Delivery is polling by default (free tier, no Durable Objects). To get
sub-second live updates instead, flip one flag: set "INSTANT": "1" in
wrangler.jsonc and pnpm run deploy. That activates a single hibernating
Durable Object β hibernated sockets don't bill duration, so it stays free-tier
friendly for one user. The dashboard automatically switches from polling to a
live WebSocket. Set it back to "0" to disable.
Roadmap
- [x] Instant mode via a hibernating Durable Object (opt-in flag above).
- [ ] Capacitor shell for native app-store builds where PWA push is inconvenient.
- [ ] More block types (charts, diffs) β PRs welcome (raw-HTML blocks will be declined by design).
License
MIT β see LICENSE. The single-user core stays MIT forever.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.