Rocky / Hermes Setup Dashboard

Identity / profile

• Assistant name: Rocky
• User: James Domingo
• Team: NextPay
• Role focus: Product Engineer for payment collection products, specifically NextInvoice and NextCollect
• Preferred style: brief, proactive, low-noise, actionable
• Primary assistant channel: WhatsApp DM
• Timezone: Asia/Manila
• Usual workday: about 12 PM to 8 PM PHT

Runtime status

• This chat is running via WhatsApp/API gateway, not a local hermes CLI binary inside the tool sandbox.
• hermes command in current shell: not installed / not on PATH
• Active background processes started by this session: 0
• Active scheduled Hermes cron jobs: 9
• Messaging target discovered: whatsapp:James Domingo (dm)
• For cron delivery back to this chat, use deliver: origin or omit deliver.

Filesystem / source checkout observed

• HERMES_HOME: /home/ubuntu/.hermes
• /home/ubuntu/.hermes exists but is root-owned in this sandbox, so direct file migration writes were blocked here.
• Hermes source checkout exists at /workspace/hermes-agent.
• Source branch: main
• Source commit: 601e5f1d5

Active cron jobs recreated from Rocky/OpenClaw

All deliver to origin, this WhatsApp chat, and are prompted to return NO_REPLY when there is no useful fresh content.

1. morning-briefing — ID 8e689b473645 — 0 0 * * * UTC = 8:00 AM PHT daily
2. prework-briefing — ID 46914f1d2af7 — 30 3 * * 1-5 UTC = 11:30 AM PHT weekdays
3. calendar-reminder — ID 8ca0cb6eb567 — */15 0-11 * * * UTC = every 15 mins, 8 AM-7:59 PM PHT
4. github-activity — ID 516544652f88 — 0 3 * * 1-5 UTC = 11 AM PHT weekdays
5. daily-intentions-ask — ID e8494fb5bf18 — 10 4 * * 1-5 UTC = 12:10 PM PHT weekdays
6. focus-nudge — ID cde985c8dabf — 0,30 4-11 * * 1-5 UTC = every 30 mins work hours
7. work-wrap — ID 3c3116b8a82d — 0 12 * * 1-5 UTC = 8 PM PHT weekdays
8. school-weekly-plan — ID a5b362dbd3eb — 0 11 * * 0 UTC = Sunday 7 PM PHT
9. school-daily-check — ID 2ae7d3246470 — 30 0 * * 1-6 UTC = 8:30 AM PHT Mon-Sat

Key Rocky/OpenClaw behavior ported

• Current calendar/email/GitHub/message/status answers require live/fresh checks.
• Stale reports are hints only, not truth.
• Automation relays suppress empty output, SKIP, NO_REPLY, thinking/tool markup, stale/missing report notices, and repeated low-value failure messages.
• Proactive nudges should be useful and low-noise.
• School/study planning should use early calendar blocking and conservative buffers.

Important skills

• james-current-state-checks
• james-daily-accountability
• quiet-relay-filter
• google-workspace
• claude-code, opencode, codex
• github-auth, github-pr-workflow, github-code-review
• hermes-agent, webhook-subscriptions, native-mcp, mcporter

Setup checklist for a proper always-on Hermes machine

curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
hermes setup
hermes doctor
hermes profile create james-domingo
hermes profile use james-domingo
hermes model
hermes gateway setup
hermes gateway install
hermes gateway start
hermes gateway status

Then from the WhatsApp DM, run /sethome.

Credentials/integrations to configure

• Model provider key, e.g. OPENROUTER_API_KEY or equivalent
• Google Workspace OAuth for Calendar/Gmail/Drive
• GitHub auth
• WhatsApp pairing
• Slack/Matrix bridge credentials if you want Slack monitoring
• Blackboard/school login mechanism if available

Gaps / things to finish

• Direct filesystem migration could not write into /home/ubuntu/.hermes in this sandbox because it is root-owned.
• The Drive migration bundle was redacted, so old secrets/tokens were intentionally not imported.
• Google Workspace auth needs verification on the actual always-on machine.
• GitHub CLI/auth was not available in this sandbox.
• Slack/Matrix/Blackboard live integrations need to be set up on the target host.

Recommended target architecture

• One small always-on VPS or home server.
• Hermes installed under a normal non-root user.
• ~/.hermes owned by that user.
• Gateway installed as a user systemd service.
• WhatsApp paired and set as home.
• Cron jobs delivering to origin/WhatsApp.
• Secrets stored only in ~/.hermes/.env or Hermes auth stores.