What Landed
Two unrelated items today. Matthew Berman detailed the agentic coding practices separating casual and expert Claude Code / Cursor users: CLAUDE.md-style config files, reusable skills, trigger-based automations chained with goal-bounded loops, and migration to cloud agents for parallel scale — plus a flagged unsolved problem, merge/deploy contention when many agents compete for main branch (Cursor is reportedly building a Git alternative for this). Separately, Nate B. Jones argued Apple's App Intents framework is the registration layer that makes app actions callable by Apple Intelligence, and that apps without it become invisible to OS-mediated AI workflows.
Why It Matters
Berman's material is tactical, not strategic: none of it changes vendor positioning or buying criteria, it's operational guidance for teams already committed to agentic coding tools. The merge-contention gap is worth tracking as a capacity constraint once clients run agents at scale, but there's no product decision to make on it yet. Jones's Apple point has real enterprise relevance, but only for organizations building or maintaining first-party Apple apps: App Intents is a near-term integration requirement, not a wait-and-see item, since Apple Intelligence will route around apps that don't declare callable actions.
Worth Raising With Customers
- If a customer has an iOS/macOS app roadmap, ask whether App Intents is scoped for 2026 releases — treat it as a checklist item alongside App Store compliance, not a nice-to-have.
- If a customer is running multiple coding agents in parallel today (Cursor, Claude Code, etc.), ask how they're handling merge conflicts at scale — there's no vendor-standard answer yet, so their current workaround is worth documenting as a risk, not a solved problem.