๐ 2026-11-16 โ Telegram, hosting decisions, GitHub, and this wiki
Daily log ยท what we built, decided and learned together
Noty connected to Telegram: BotFather token wired into the profile .env (TELEGRAM_BOT_TOKEN + allowed user 181318024). Bot **@notyos161110_bot** online โ gateway polling confirmed in profile logs. Key rule established: one token per bot, DMs are separate chats, group chat with topics comes later.
77 MCP tools explained: Notion exposes its full API as MCP tools โ search/read, create/edit, databases, comments, meetings, users. Pruning to ~10-15 via hermes mcp configure noted as optional context savings.
Group chat with topics designed: one topic per agent, admin+Manage Topics required, bots added as members. Blocked on Roman creating the group + Noty token flow (deferred to 'tomorrow').
Hosting strategy settled: NO new server, NO domain. Cloudflare Pages chosen for static pages (free *.pages.dev, HTTPS, global CDN); VPS stays for Hermes + Noty with outbound-only networking. Tailscale rejected by user โ do not revisit.
Status server built on VPS (Python stdlib, token-protected, port 8643) then superseded by the real thing: **Cloudflare Pages project roman-agents deployed** โ https://roman-agents.pages.dev with bot cards + done-task list.
Site iteration: interactive agent cards (click โ detail pages /agents/hermes.html, /agents/noty.html), tasks.html with per-agent filter chips, then **Done Tasks deleted** on request (404.html added to fix the SPA-fallback bug where deleted pages returned the homepage with 200).
GitHub MCP connected: fine-grained PAT in .env, remote server api.githubcopilot.com/mcp, header auth ${GITHUB_MCP_TOKEN}. Verified with get_me โ **romanogram1**. OAuth path abandoned (no dynamic client registration support).
This wiki proposed and built โ you're looking at it. Same design system, generated from real conversation history.