Kilroy (Hermes trial) — Phase 2 Integrations

Date: 2026-07-23 (session 60) · Type: status · Status: live (trial)

Phase-2 wiring for the Hermes Agent trial bot (Kilroy, Telegram @Hermes_Unlikely_bot). Rob/production untouched.

Vault access (read-only): custom stdio MCP server ~/.hermes/mcp-servers/mostly-vault/server.py exposes vault_search / vault_read_note / vault_list over this vault and the project vault. mostly-mcp itself is Windows-only (SFTP writer) so it could not be reused on the VPS. Vault writes from Kilroy are pending Dustin’s decision — until then Kilroy proposes notes for Dustin to add.
Deliverable mode: native Telegram file/image attachments — no config needed (gateway path-scan).
Cron shadows (3 of Rob’s 13, ET schedules preserved, deliver → Dustin’s Telegram): Morning Briefing 8:00 wkdy, EOD Summary 18:00 wkdy (both pinned claude-sonnet-4-6), Backup Health Check 6:00 daily (no-agent script, zero LLM). API key read from ~/.hermes/.env at runtime — fixes Rob’s inline-key-in-cron pattern.
Webhook (bucket-2 path): HMAC-V2 deliver_only route unlikely-api-notify on port 8644 → Dustin’s Telegram, zero-LLM. Proven from unlikely-api via new standalone services/kilroy_notify.py (entirely-api 06dc25b) — the candidate replacement for the OpenClaw hooks bridge in whatsapp_service. ufw scoped: only the unlikely-api compose subnet may reach 8644; not internet-exposed.

Connections: unlikely-api →(test-posts to)→ Kilroy webhook route; Kilroy →(reads)→ mostly-vault + project-vault.

Mostly Wiki