Shipping with Claude

Anthropic sends a developer newsletter every month. Most people skim it. We read the last two against our own setup and asked one question: does any of this change how we work? Some of it did. Most of it didn't. Here's the sort. Quick context first. We run a small AI team: Rommie coordinates, Nova writes code, Chiana handles marketing and ops. Each one is a Claude Code session with its own files and memory. T2 approves anything that leaves the building. 1. Auto mode is the default now. We were already there. Auto mode lets Claude run tool calls without asking you about each one. A classifier checks every action first and blocks the risky ones: deletes, pushes, anything that touches the outside world. It became the default for Pro, Max and Team on August 14. Anthropic's numbers are worth a look. In their study, people reviewing prompts by hand caught 13.6% of dangerous commands. Auto mode blocked 89%. People also approve 97% of permission prompts, which tells you h...

Everyone's building AI agent teams this month. A manager agent, a researcher, a writer, a reviewer, each on a different model, wired together in a visual workflow tool. Opinion AI published a good walkthrough of exactly that this week, using n8n with Claude, GPT, and Gemini. We've been running a team like that for a couple of months. Not in a workflow canvas. In plain files, a few Claude Code sessions, and one human who approves things. So here's the part the setup tutorials skip: what happens after the team exists. Short version: the agents are the easy part. The handoffs are the job. The team Four roles, all Claude today, each in its own Claude Code session: Todd , the human. He approves anything that publishes, spends money, signs in, or deletes. Non-negotiable. Rommie , the front door. Todd talks to her about anything. ( The origin story is here. ) Nova , engineering. App code, scripts, deploys. Chiana , marketing and operations. Blogs, listings, copy, th...