Field guide / sub-domain

AI Agents: Infrastructure

6

sources in this field

Updated June 13, 2026

Current thesis

The shortest path to orientation.

The agent infrastructure layer has consolidated from a sprawl of point tools into a recognizable production stack of named primitives and now includes a mature authentication and session management layer: AgentCookie synchronizes browser sessions between a daily Mac and a dedicated MacMini agent machine via Tailscale peer-to-peer sync, solving the problem of agents waking up logged out of services — compatible with OpenClaw, Hermes, and other runtimes. Agent debugging has formalized as a medical-diagnosis model: treat bugs as organ failures, not model failures — identify whether gbrain (memory), OpenClaw (approvals/actions), or trajectory bundles (self-check) failed, and AI hallucinations diagnosed as "confabulation" unlock targeted fixes. The original stack still anchors the layer:: Pipecat (sub-200ms voice), browser-use (web navigation), Mem0 (persistent cross-session memory), Composio (OAuth across 1,000+ apps, one-click integration), RAGFlow (layout-aware retrieval), Dify (visual workflow building), with Mastra as the TypeScript-first framework (1.77M monthly npm downloads, YC). Firecrawl has become the default web-search layer, auto-pairing with Browserbase to select scraping vs. full browser interaction per task; Browserbase now also distributes researched web-agent skills, and anti-detection browsers like Camofox push browser automation down to spoofed browser/runtime properties. Around these primitives sit observability and routing infrastructure — OpenClaw Studio (self-hosted dashboards, approval gates, cron) and smart routers (ClawRouter scoring requests across 14 dimensions in <1ms, cutting blended cost from $75/M to $3.17/M).

Cost architecture is foundational: 80% of agent tasks are janitorial and don't need frontier intelligence, so hierarchical model routing by complexity (the 80/15/5 routine/moderate/hard distribution) yields ~10x cost reduction; accessibility-tree browser output and local self-improvement plugins extend that cost discipline into runtime behavior. Memory is a distinct context form: the "napkin" scratchpad (not session history, not static plans) plus self-logging of mistakes produces compounding improvement by session five, and claude-smart turns those corrections into explicit reusable rules across projects. Configuration is converging on three files for articulate agents — SOUL.md (brutally specific constitution), USER.md (~4000-word user model), AGENTS.md (operational rules) — because generic instructions revert output to ChatGPT. Underneath, MCP is becoming the survival-level integration protocol for tool vendors, autoswarm/Hyperspace platforms generalize Karpathy's autoresearch loop, remote-device/Tailscale networks give agents durable execution surfaces, and BitNet 1-bit LLMs signal viable local inference on commodity hardware. The Cross-Cutting Patterns from the parent topic are preserved at the end of this file as the canonical synthesis index across all sub-topics.

Evidence board

Claims worth carrying forward
01

AgentCookie synchronizes browser sessions between your daily Mac and a dedicated MacMini agent machine, keeping authentication cookies in sync so [[ai-agents]] wake up already logged into services

02

The tool uses Tailscale for encrypted peer-to-peer session syncing with no cloud middleman, enabling [[ai-agents/infrastructure]] setups where agents run on separate hardware

03

Works with OpenClaw, Hermes, and other agent runtimes by maintaining continuous session sync, solving the authentication problem for [[ai-agents/automation]] workflows

04

Enables a multi-Mac setup where your primary browsing machine feeds authentication state to a dedicated agent machine running macOS

05

Set up a single persistent Codex thread as a 'chief of staff' that manages all other project threads and maintains context from Slack integrations

06

Configure the chief of staff thread to automatically spin up new project threads when starting workstreams, inheriting relevant context from Slack and other sources

07

Implement regular 'heartbeat' check-ins where the chief of staff thread monitors project threads and routes relevant Slack updates to appropriate project contexts

08

Enable Codex to self-manage by having it create threads, search existing ones, organize content, pin important items, and spin up parallel worktrees for concurrent tasks

Adjacent fields

Key voices

Latest evidence

Recent additions

All synthesized insights →