automation

Automating the bottleneck means finding the constraint that sets your pace and pointing Claude at it: four working rules distilled from Anthropic's own engineers.

A routine is a saved instruction Claude runs on its own, on a schedule or an incoming signal. What it replaces, and why an unattended run has to be written tighter than one you watch.

When an agent hits the same problem twice, encode the fix as a lint rule, CI check, or steering-file instruction that every future session inherits.

A rerun loop makes the agent redo its own work until a check passes. Script the repetitive half of a skill, end it with a pass or fail verdict, wrap both in a loop, and keep a human at the checkpoints where errors are expensive.

Cody Schneider builds agents that find leads and post content while nobody watches. The method: turn the human process into scripts on a schedule, and call the model only where a judgment is needed. Both of his builds, tool by tool.

Grok Bot, the new beta app from SpaceXAI and Cursor, gives you a team of AI agents that keep working with your laptop shut, each on its own cloud computer. How work gets routed between them, how recorded skills and triggered routines run themselves, and which work should stay at your desk.

Allie K. Miller runs 34 AI agents, and her day is reviewing what they propose, deciding, and handling escalations. What an agent needs before it can start work you never assigned (written goals, fresh context, tools, triggers), the four-stage ramp from one agent to a workforce, and the watchdog jobs worth assigning first.

Boris Cherny, who created Claude Code, maps four steps between chatting with an AI and a system that starts work you never assigned. Find your step from the bottleneck you feel, and make the one change that moves you up.

Agent workflows run one step after another by default, which is the slowest shape. Ask at each step whether it needs the result of the step before it, then re-shape the work: fan out independent steps, route requests down branches, loop until a check passes, and cap what each shape can waste.

Turn a tested task into a reusable skill, choose where it runs, and catch failed work before it wastes more time.