Field guide / sub-domain

AI Agents: Automation

34

sources in this field

Updated September 16, 2026

Current thesis

The shortest path to orientation.

This synthesis records claims and practices from the cited sources; reported outcomes and product capabilities have not been independently verified.

Automation consolidates around parallel subagents with scoped access and hard guardrails. Scheduled Claude routines operate as 'night shift' labor with minimal setup. The approval boundary is reversibility: finish undoable work (drafting, tagging, research) autonomously; park irreversible actions (sends, spending, publishing, deletions) for human review. An n8n inbox-management agent pulls replies, classifies sentiment, checks availability, drafts responses, and pushes both to Slack for review before sending—speed-to-lead (minutes vs. hours) materially changes conversion. Setup takes roughly two minutes with a single prompt. Infra manager agents enforce hard guardrails distinct from optimization: never pause/unpause sending accounts (kills warmup) and never quarantine domains on thin data—these are treated as constants the bot never overrides. Parallel workflows require tight loops to prevent unproven changes from shipping.

Evidence board

Claims worth carrying forward
01

Cold outbound GTM is decomposed into four persistent GrokBot agents—list builder, outbound copywriter, campaign manager, infrastructure manager—each owning one artifact (lead list, copy, campaign build, sending health) with one owner and one definition of done.

02

GrokBot gives each agent a persistent cloud computer (browser, filesystem, terminal) that logs into apps with real credentials instead of APIs, keeps running when the laptop is off, delegates to other bots in a shared thread, and can convert a recorded human workflow into a repeatable 'skill'.

03

GPT-6 Astra (Sept 2026) is used as the coding layer: state of the art on computer use/browsing/software engineering, 1M token context, $10/$50 per million input/output tokens; it writes scrapers, enrichment jobs, and reporting queries behind the GrokBot agents.

04

Reliable multi-agent handoffs rest on three mechanisms: naming as join key (campaign name = list name so no bot has to ask what belongs where), task-state-as-trigger (marking a task complete fires a webhook waking the next bot, no human forwarding needed), and 'blocking out loud' (a bot missing an input posts what it needs and stops rather than guessing).

05

Porting existing human SOPs to agents required little rewriting because handoff points already existed where one human stopped and another picked up—suggesting well-documented human workflows are a low-friction path to agentic automation.

06

A/B testing discipline for AI-generated outbound copy: enforce 'one changed variable per script' (e.g., only offer framing moves, everything else frozen) so that performance data collected two weeks later remains attributable to a single cause.

07

When an agent underperforms, the root cause is usually a missing numeric threshold rather than a bad model—an unspecified judgment call gets guessed by the agent, and a repeated guess hardens into an unintended pattern.

08

Infra manager agent enforces hard guardrails distinct from optimization: never pause/unpause a sending account (kills warmup) and never quarantine a domain on thin data (a few sends in the lookback window proves nothing)—these are treated as constants the bot never overrides.

Adjacent fields

Key voices

Latest evidence

Recent additions

All synthesized insights →

Charlie Hills

Anthropic's Four Agent Loop Types: Turn, Goal, Time, Proactive

Anthropic's Claude Code team formally defines agentic 'loops' as cycles of work repeated until a stop condition is met, categorizing them into four types (turn-based, goal-based, time-based, proactive) by what gets handed off. Charlie Hills synthesizes the framework with practical commands (/goal, /loop, /schedule, skills) and a warning that every loop still needs an explicit stop condition or it burns tokens unattended.

The Startup Ideas Podcast (SIP) 🧃

Treat Claude Code Like an Employee: A 9-Part Operating System

A structured framework for using Claude Code as an 'AI employee' rather than a chatbot, covering repo-as-workspace, memory files (CLAUDE.md/roadmap.md/review.md), plan-mode briefs, scoped tickets, visual verification, three-layer review, scheduled routines, parallel agents, tiered permissions, and reusable skills/hooks — demonstrated via a med-spa missed-lead responder build.