gem-hunter
主要言語: TypeScript
Hermy HQ — a self-hostable mission-control dashboard template that pairs with your own local Hermes agent over a Postgres message bus. Send it to your Hermes and it onboards you step by step.
Your own mission control for a self-hosted AI agent.
Hermy HQ is a self-hostable dashboard template that pairs with your own local Hermes agent. The website is your cockpit: dispatch work, review the agent's plans, approve anything with side effects, browse its memory, and watch it run, all from one place. Your Hermes stays on your own machine; the website and the agent talk to each other through a shared Postgres database acting as a message bus.
It is a template and starting point, not a hosted product. You bring your own database, your own Hermes, and your own API keys. Everything is configured through environment variables.
Important
🤖 If you are an AI agent reading this repository
The person who gave you this link wants you to install Hermy HQ for them. Do this:
ONBOARDING.md, a complete step-by-step installer written for you..env, database, local run, Vercel deploy, and the bridge.ONBOARDING.md is the full guided install. Start there.
ONBOARDING.md. It onboards you step by step, pausing for each secret.Cockpit
Hermes control hub (/hermes)
Memory
Work & content
Some features need your own API keys (YouTube, X/Twitter, OpenAI, etc.). They are all optional and configured via env — the core dashboard runs without them.
The deployed website never talks to your agent directly. Both sides read and write the same Postgres database, which acts as a message bus. A small bridge process runs on the machine where Hermes lives.
┌───────────────────────┐ ┌────────────────────────┐
│ Hermy HQ (website) │ │ Your machine / server │
│ Next.js on Vercel │ │ │
│ │ │ ┌───────────────┐ │
│ • dispatch requests │ │ │ hermes-bridge │ │
│ • approval inbox │ │ │ (bridge.mjs) │ │
│ • activity / runs │ │ └──────┬────────┘ │
│ • memory wiki │ │ │ hermes CLI │
└──────────┬────────────┘ │ ┌──────▼────────┐ │
│ │ │ Hermes │ │
│ │ │ agent │ │
│ │ └───────────────┘ │
│ └───────────┬────────────┘
│ │
▼ ▼
┌────────────────────────────────────────────────────────┐
│ Postgres (message bus) │
│ AgentRequest · AgentEvent · HermesTask · HermesMemory │
│ DataStore · Brief · … │
└────────────────────────────────────────────────────────┘
AgentRequest. Safe requests are
queued; anything side-effecting is awaiting_approval until you approve it in
the inbox.queued/approved requests
via the hermes CLI, and writes results back. It never runs awaiting_approval.HermesTask), cron +
health (DataStore), memory (HermesMemory), and activity (AgentEvent) back
into Postgres, where the website reads them.Nothing on your machine is exposed to the internet — the bridge only needs outbound
access to Postgres and your local hermes CLI. See
hermes-bridge/README.md for details.
hermes CLIhermes CLI on PATH)git clone <your-fork-url> hermy-hq cd hermy-hq npm install
cp .env.example .env
Open .env and fill in at least the required core vars: DATABASE_URL,
POSTGRES_URL, NEXTAUTH_URL, NEXTAUTH_SECRET, GOOGLE_CLIENT_ID,
GOOGLE_CLIENT_SECRET, ALLOWED_EMAILS, and NEXT_PUBLIC_OWNER_NAME.
Every variable is documented inline in .env.example.
Generate a secret with:
openssl rand -base64 32
npx prisma db push
npm run dev
Open http://localhost:3000 and sign in with a Google account whose email is in
ALLOWED_EMAILS.
npm i -g vercel # if you don't have it vercel # link + deploy a preview vercel --prod # production
Then:
.env in Project → Settings → Environment
Variables.NEXTAUTH_URL and NEXT_PUBLIC_BASE_URL to your production URL.https://<your-domain>/api/auth/callback/google.On the machine where Hermes lives, set up the bridge so the bus connects:
cd hermes-bridge npm install DATABASE_URL='postgres://…same as the website…' HERMES_BOARD=default node bridge.mjs
You should see hermes-bridge up … and a "Bridge connected" event appear in the
website's activity feed. To keep it running, install it via launchd (macOS) or
systemd (Linux) — full instructions in
hermes-bridge/README.md.
src/ Next.js App Router (dashboard, /hermes, memory-wiki, content-os, …)
prisma/ schema.prisma (message-bus + feature models)
hermes-bridge/ the bridge that runs on your machine next to Hermes
.env.example every env var, documented
ONBOARDING.md copy-paste prompt to have your Hermes install this for you
Hermy HQ is designed so the agent can act, but not surprise you:
sideEffecting and land in the
Approval Inbox as awaiting_approval. The bridge will not run them until you
approve.hermes CLI — nothing inbound.ALLOWED_EMAILS.Provided as a template for you to fork, self-host, and adapt. Add the license of your choice before publishing your own instance.