Freewrite
A planning and tooling day. Most energy went into comparing AI tool costs and thinking about the Hermes agent fleet — two topics that keep coming back. Also resolved a loose end on the daily news brief email by adding source links, and got more clarity on the Composio Microsoft To Do issue (still blocked on a permissions scope).
Big Things Today
- Decide on Claude Code Team Premium vs MiniMax Ultra-Highspeed based on today’s comparison — key factor is team size and use case
- Re-attempt Composio Outlook reconnection with Tasks.ReadWrite scope to fix Microsoft To Do 401 error
Conversations
AI Tooling
Minimax (Claude Code Team vs MiniMax comparison)
Detailed cost and quota comparison between Claude Code Team Premium (150/month, no seat minimum). MiniMax wins on cost flexibility for solo/small teams; Claude Code wins on context window (1M vs 204K tokens), admin controls, and overflow usage. Key uncertainty: Claude Code doesn’t publish exact token quotas — all numbers are third-party estimates. → See minimax-litellm-cost | minimax-token-procurement
Composio AI agent integration platform
Continued attempt to create tasks in Microsoft To Do via Composio. Still hitting 401 — Outlook connection is missing Tasks.ReadWrite Microsoft Graph scope. Fix: reconnect at composio.dev with correct scope, or switch to native Microsoft 365 connector in Claude.ai.
→ See composio-mcp-connector
Productivity & Automation
LLM-powered news search and summarization sites
Updated the daily news brief email template to include clickable source links on each bullet. Every section now includes direct links to source articles (TechStartups, Analytics Insight, Thailand Business News, etc.). Change applied via Composio email tool. → See pkm-daily-summary
Using Claude desktop on multiple computers
Clarified that Cowork desktop app requires the PC to stay on and logged in for scheduled tasks to fire. Three options explored: (1) disable sleep, (2) Windows wake timers, (3) cloud VM ($5/month VPS on DigitalOcean or Hetzner). Cloud VM is the most reliable long-term approach. → See cowork-cloud-vm-scheduling
Agents & Architecture
Hermes benefits and capabilities (fleet architecture)
Early exploration of running multiple specialized Hermes instances — one per life area (work, personal, health, etc.) vs. Hermes sub-agents under a single orchestrator vs. a hybrid hierarchy. No final design yet; conversation ended at the clarifying-questions stage. → See hermes-agent-orchestration
Hermes benefits and capabilities (AGENTS.md + MEMORY.md verification)
Confirmed that Hermes natively supports both AGENTS.md and MEMORY.md. AGENTS.md is one of four interchangeable project-context formats (alongside CLAUDE.md, CONTEXT.md, README.md) and is discovered progressively across subdirectory hierarchy. MEMORY.md is agent-curated persistent memory capped at 2,200 characters — not a hand-authored config. Full configuration surface mapped: SOUL.md → USER.md → AGENTS.md → MEMORY.md → FTS5 sessions → skills library, plus 8 optional external memory plugins. → See hermes-agent-configuration
Open Tasks Surfaced
- Reconnect Composio Outlook with Tasks.ReadWrite scope
- Decide: disable PC sleep, configure wake timers, or provision cloud VM for Cowork scheduling
- Explore Hermes fleet architecture — define life areas and agent roles before committing to structure
- Consider Claude Code Team vs MiniMax for next procurement decision (team size is the deciding factor)
Insights Worth Developing
- Cloud VM vs local machine for always-on AI agents — reliability vs convenience tradeoff
- MiniMax is cost-optimal for solo AI workflow testing; Claude Code Team only makes sense at 5+ seats
- Hermes fleet as life OS — specialized agents per domain rather than one generalist agent
- AGENTS.md and MEMORY.md as the two key Hermes customization points — project context vs agent memory
Updates — 2026-05-22 (evening)
Hermes Configuration Surface Verified
Deep dive into Hermes native file support confirmed: AGENTS.md (project context, 4-level hierarchy, interchangeable with CLAUDE.md), MEMORY.md (agent-curated, 2,200-char cap, not hand-authored), plus SOUL.md, USER.md, FTS5 session database, skills library, and 8 optional external memory plugins. Key distinction: MEMORY.md is written by the agent over time — don’t treat it like a config file. Reference note created. → See hermes-agent-configuration