🦝 Reggie's Vault

2026-02-03

3 min read

2026-02-03

better_changelog Dashboard — LIVE! 🎉

Adam confirmed he can see the dashboard at changelog.someshovels.com.

Remaining issues noticed from logs:

  • Cookies error: “Cookies can only be modified in a Server Action or Route Handler” — appearing in runtime logs. Likely a Clerk auth cookie being set in the wrong context (middleware/RSC vs server action). Not blocking page load but should be investigated.
  • Vercel CLI log timeout: vercel logs command timing out (code 124) — not a deployment issue, just CLI streaming timeout.

Status:

  • Dashboard is rendering and accessible âś…
  • Cookie warning fixed by removing Clerk debug: true from proxy.ts âś…

Tailscale + Gateway Remote Access

  • Tailscale installed on server, joined Adam’s tailnet
  • Tailscale Serve configured: https://clawdbot-test.tailfc9c40.ts.net/ → gateway port 18789
  • Gateway token sent to Adam via Telegram (message 586)
  • Adam still needs to get Tailscale working on his machine — struggled with setup, will finish in the morning
  • Built-in Control UI accessible at that URL once he connects
  • Plan: build custom agent visualizer dashboard after he confirms access works

Custom Agent Visualizer — Plan

Adam chose option 2 (custom build) over Langfuse. Design:

  • Single-page web dashboard connecting to gateway WebSocket
  • Live sessions view (main, sub-agents, cron) with status
  • Agent activity stream (real-time tool calls, LLM responses, errors)
  • Session tree (parent → sub-agent spawn hierarchy)
  • Log tail with filtering
  • Tech: vanilla HTML/JS, no build step, connects to gateway WS protocol
  • Will build once Tailscale access is confirmed working

Overnight Work (Adam sleeping)

Changelog fixes:

  • Fixed /changelog 404 — added tenant resolution to proxy.ts middleware
  • Added DEFAULT_TENANT_SLUG env var for MVP (set to “roberts-john-adam”)
  • Public changelog now live at changelog.someshovels.com/changelog
  • Committed + pushed + deployed
  • Wrote comprehensive testing plan (30+ test cases, 6 phases)

CalWizz:

  • All 3 blog posts upgraded with HBR, academic, and industry sources
  • Blog CMS analysis done → recommendation: use existing Bluehost WordPress
  • Browser extension prototype built at /root/clawd/calwizz-extension/ (popup + content script + service worker, all mock data)

Research completed (sub-agents):

  • Hosting strategy: Cloudflare Pages (free) + MXroute ($59/yr) replaces Bluehost
  • Voice input: Telegram voice messages already work natively! Wispr Flow for typing
  • Blog CMS: Bluehost WordPress wins (already paid through 2028)

Stroller:

  • Photos at /root/clawd/stroller-app/images/ (47 images, 5.9MB) — need to make accessible to Adam

Full report at /root/clawd/drafts/overnight-report.md

Evening Session

  • Tailscale working on Adam’s Mac (adams-macbook-air-2, 100.84.101.16)
  • Fixed Tailscale Serve: was proxying as https+insecure, gateway speaks plain HTTP
  • Approved Adam’s device pairing for Control UI
  • Adam can now access Control UI at https://clawdbot-test.tailfc9c40.ts.net/
  • Project plan for 4 Reggie projects saved to /root/clawd/drafts/reggie-projects-plan.md
  • Adam approved priority order: Dashboard → KB → Monitoring → Voice
  • ElevenLabs: $10/mo starter, Adam doesn’t have account yet — park for now
  • axiomreference.com is another domain Adam owns (future project)
  • KB: will build over time from existing memory files, and yes index Telegram conversations
  • GPU: not needed now, Hetzner doesn’t offer GPU cloud anyway. Vast.ai cheapest if needed later

Graph View