Sunday 27 July 2026

Agent HQ

Where the CARE build left off, what changed in three and a half weeks, and what's worth stealing from the last 30 days. Two Opus research agents, ~250 items, 9 sources.

Today

Say go on the CARE build resume
The scaffold is safe in GitHub; only the container and Phases 2–4 remain. Three blockers are still yours: Todoist API token, the Nanz message, Möbius Sync on the phone.
Approve the design change: herdr replaces tmux
The blueprint's "skip herdr" call is stale — details in The Herd below. This is the one real edit to the plan.
Try dynamic workflows — type ultracode in any prompt
GA on your Teams plan (Claude Code v2.1.154+). Background JS orchestration, 16 agents concurrent, results stay out of your context window. Free to try today.
Replace the Perplexity API key
It returned 401 (expired) during today's research runs. Lives in ~/.claude/.env.
Read one thing: Coles, "Herding agents with herdr"
Your exact target architecture — agents on a remote Linux box, Mac as thin client, one workspace per worktree. coles.codes ›
Pick the phone layer
Collie (PWA over your tailnet, push when an agent blocks) vs herdr-remote (Telegram) vs the original La Terminal + mosh. My lean: Collie — compared below.

Checkboxes save on this device — use it as a working list.

Where we left off

2 July, the Fable session. Your "Marketing strategy with Fable" brain dump became the CARE blueprint: a portable, always-on work system on a new homelab container — verified two-tier memory, Todoist, Syncthing, four scheduled jobs, Hermes as the phone front door. The session died mid-build when Fable usage ran out. The blueprint survives: CARE — system blueprint ›

Built and safe in GitHub (pushed 2 Jul, 13:54)
care-system — the portable seat
CLAUDE.md, AGENTS.md, settings.json with pinned plugins, .mcp.json, 26 skills, memory tiers, bootstrap.sh, helper scripts. 751 files.
care-vault — the knowledge shell
Dashboard, strategy files (goals / backlog / calendar / team), projects index, legacy archive.
Never happened
CT105 "care" container
Doesn't exist on Proxmox — only CT101 and CT103 are running. Phase 0 is still open.
The four scheduled jobs
cio-state, metrics→reporting, briefing, project-sweep — jobs/ holds only a README.
Verified docs layer
Pricing, features, help-map, team-roles — the layer that stops Fable re-deriving facts.
Hermes work profile, Syncthing, phone setup
Phases 3–4 untouched.
Still waiting on you
Todoist token · Nanz message · phone installs
The same three blockers from July. The Nanz draft is in the blueprint, ready to paste.

The herd

The blueprint parked herdr as "young, replaces tmux, no notifications." That call is now stale. Since the May safety scan it went from ~1.5k to 21,209 stars and v0.5 → v0.7.5, and the parts that were missing are exactly what shipped: a socket API with event subscriptions, a CLI for driving agents (herdr agent start / prompt / send-keys / wait), and an integration that reports real blocked/working/done state (herdr integration install claude).

The @tonbistudio post you sent is the proof of the pattern: Hermes supervising other agents through herdr's socket API — which is, almost word for word, the "hermes should be able to check in on active claude code sessions" line from your July brain dump. Their status skill is open-sourced as flock-check › — read-only, well-designed, and worth porting rather than writing our own cc-status script as the blueprint planned.

What this changes for CARE
Herdr becomes the multiplexer on the care container
Named session per project, one workspace per git worktree (the emerged convention). Detach ctrl+b q; agents keep running.
Hermes check-ins via socket API, not tmux scraping
flock-check treats herdr's reported state as authoritative and scrollback as context only — better judgement than anything we'd hand-roll. Port it for Hermes and as a Claude Code skill.
The blueprint's one open question closes
herdr --remote thin-client mode bridges clipboard image paste from the Mac — the exact Cmd+V-over-SSH gap cmux couldn't confirm.
Phone options that didn't exist in July
Collie — my lean
Herdr plugin + PWA served over tailscale serve (you already run the tailnet). Floats the blocked agent to the top, pushes a notification when one needs input. github ›
herdr-remote — the Telegram-flavoured alternative
Menu bar + phone + Telegram through a free tunnel. Overlaps with what Hermes already gives you. github ›
Caveats — carry these into the build
No sandboxing
"herdr does not sandbox your agents" — awareness and persistence only. With skip-permissions agents on the homelab, isolation is our problem to solve in the same pass (see Fresh finds).
Agent detection is the weak spot
Process detection breaks on renamed binaries — Codex runs as codex-raw and goes unrecognised (issue #1354). Fix: install the integrations; diagnose with herdr agent explain.
v0.7.5 upgrade note + muscle memory
Plugins went global per-user in 0.7.5 (per-session installs need redoing). Prefix is ctrl+b — collides with tmux habits, and keybindings are a common complaint. Still pre-1.0.

Plan, revisited

Keep
Almost everything
Two-tier memory with approval-gated core · Todoist · Syncthing fabric · docs/ vs data/ split · the four jobs · honest headless-vs-laptop MCP split · Granola pipeline · $0/mo. All of it held up against three weeks of ecosystem movement.
Change
tmux → herdr on the care container
And the planned cc-status SSH-scraping script becomes a flock-check-style socket-API skill for both Hermes and Claude Code.
Change
Remote access simplifies
cmux stays for cloud agents, but day-to-day attach becomes SSH + herdr (or herdr --remote when you need clipboard images). The planned careshot helper is probably unnecessary now.
Change
Phone terminal decision reopens
La Terminal + mosh still works as the raw fallback, but Collie's blocked-agent push over the tailnet covers the actual use case — "does anything need me?" — better than a terminal does.
New
Sandboxing pass in Phase 0
Herdr's named gap. The pattern with traction is container-per-agent (Code on Incus). We're on Proxmox — LXC-per-agent is a natural fit and keeps skip-permissions speed without the blast radius. Needs a proper design decision, flagged not solved.
New
Dynamic workflows join the toolkit
For in-session fan-out (research, audits, bulk edits) — replaces hand-rolled subagent orchestration and keeps intermediate results out of context. My call: the four scheduled jobs stay simple cron → claude -p as designed; workflows are for interactive sessions, and the bundled /deep-research (adversarial claim-checking) is a working template for how the verified-facts jobs should verify.
New
Verify, don't assume: Remote Control on Teams
Anthropic's steer-your-local-session-from-the-iOS-app launched as a Max-tier research preview in Feb and reportedly wasn't on Team plans. Worth a check before it shapes any phone decisions; third-party fallbacks exist (Tactic Remote, AgentsRoom, Nimbalyst).
Bottom line: the blueprint doesn't need a rewrite — it needs a resume, with herdr swapped in and a sandboxing decision added. Build order stays: container → verified docs + jobs → Hermes loop → parallel week → cutover. The build itself should run on Sonnet/Opus with Fable only at decision points, so usage limits don't kill it a second time.

Fresh finds

last 30 days
Dynamic workflows — the biggest unlock already on your plan
effort: very lowfirst-party

Type ultracode in a prompt (or /effort ultracode) and Claude writes a JS orchestration script executed in the background — session stays responsive, intermediate results live in variables not your context window. Caps: 16 concurrent agents, 1,000 per run. /workflows is a live progress TUI; press s to save a good run as a reusable command.

The bundled /deep-research workflow has agents adversarially cross-check each other's claims and drops what doesn't survive — a working reference implementation of your verified-facts memory idea.

Fact, first-party: code.claude.com/docs/workflows · needs v2.1.154+, all paid plans

Container-per-agent sandboxing (Code on Incus)
effort: mediumcloses herdr's gap

From the 51k-star awesome-claude-code list: Code on Incus gives each agent an isolated machine (root, Docker, systemd) with automatic threat detection; compass adds cost-tiered subagents + guardrail hooks with Claude Code/Codex parity. Inference: on your Proxmox box, LXC-per-agent is the natural translation — isolation without giving up skip-permissions speed.

awesome-claude-code

The worktree backlash — know before you generalise
watch

Trigger.dev ditched git worktrees for parallel agents: port conflicts, DB migration clashes, per-worktree service duplication, ~10GB disk across two worktrees on a 2GB codebase. They moved to GitButler virtual branches with file-level commit routing via a skill.

For your repos (vault, marketing ops — no dev servers, no migrations) worktrees are fine and this pain doesn't apply. It matters only if the codebase-access ask to Nanz turns into running the actual app.

trigger.dev/blog

Memory MCPs: crowded, fragmented — wait
skip for now

124 memory-category MCP servers catalogued; nothing has won. The closest match to your design — Mwe-MCP, human-readable markdown wiki that self-organises overnight — has 5 stars. Read it for design ideas, don't adopt. Your approval-gated two-tier design remains ahead of the market; Supermemory's benchmarks are self-reported, Cognee is the only one with peer-reviewed results.

Mwe-MCP on GitHub · mcpservers.org

Obsidian-side retrieval caught up to qmd
effort: low to evaluate

VaultSearch (BM25 + vectors + fuzzy titles, fully on-device) and Smart Connections now cover locally what qmd does. Mostly duplication for you — the delta is driving retrieval from inside the vault UI on your phone rather than only from an agent session. Also spotted: an Obsidian plugin that pushes note checklists to herdr agents as todos and ticks them off automatically — checklist-driven agent work straight from a note.

Telegram-resident agents are a recognised category now
validates Hermes

Avelina — "self-hosted personal AI assistant that lives in Telegram, persistent memory, voice, Claude-powered" — is the same shape as Hermes on CT103. Roundups now name Hermes Agent alongside OpenClaw, LibreChat, AnythingLLM as the standard self-hosted set. You're not on an island; the pattern won. The demo framing that resonates: texting your agent from a coffee shop instead of running back to the laptop.

Marketing skill packs — steal the taxonomy, not the skills
effort: lowgrowth

coreyhaines31/marketingskills is the most-cited pack: CRO, copywriting, SEO, email/lifecycle, pricing, analytics — mapped across acquisition → activation → retention. Your bespoke CIO/PostHog/Strapi skills are better fitted than anything generic, but the funnel-stage map is a good audit lens against the 26 skills already in care-system: where are the gaps by stage?

Competitive signal from the same sweep: ActiveCampaign now ships 25+ agents (campaigns, automations, insights) — CIO's peers are putting agent surfaces into lifecycle tooling.

marketingskills on GitHub

Cross-harness config + the mega-repo genre
browse, don't adopt

Portable agent config across Claude Code / Codex / Cursor / OpenCode is becoming its own category (ECC v2; a hackathon-winning repo with 28 subagents/119 skills doing 1M+ TikTok views). care-system's pinned-plugins + AGENTS.md-symlink approach is already the right idea — these are worth a browse for conventions, not wholesale adoption. Also flagged: obra/superpowers reported at 261k stars by the GitHub API — anomalously high, sanity-check before quoting.

Fine print

Housekeeping done during research
last30days plugin updated 3.3.0 → 3.18.3; your local patches reapplied cleanly (one patch is now dead code in 3.18.x — the pipeline.py Perplexity gate no longer exists).
Coverage caveats
Perplexity excluded from all sweeps (expired key, 401). Reddit rate-limited (HTTP 429) partway through both productivity runs — Reddit signal is thinner than usual; absence of a Reddit thread proves nothing.
Raw evidence on disk
Three raw dumps in ~/Documents/Last30Days/: herdr-terminal-agent-multiplexer-raw-v3.md, claude-code-workflows-and-agent-setups-raw-v3.md, self-hosted-always-on-personal-ai-agent-setups-raw-v3.md.