# Agent Tooling Earns Adoption by Augmenting Existing Workflows ## Claim An AI integration adopts faster when its installer detects and extends a developer's current toolchain instead of forcing a fresh setup. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when the existing tools are detectable and the install script can add only the missing pieces without disturbing what's already configured. - Breaks when version conflicts or platform gaps (e.g. macOS-Apple-Silicon-only) block the merge entirely, forcing a fresh setup anyway. - Does not claim this raises long-term retention — only that it lowers the friction of the first install, which is a distinct, narrower claim. ## Evidence The WordPress Studio MCP server bridges Claude Desktop to the Studio CLI. Its installer is explicitly scoped: "the installation script will only install the extra bits needed, and integrate them with your existing installation" — rather than requiring a from-scratch environment. The integration is currently limited to macOS Apple Silicon, which is itself evidence of the boundary condition: augmentation only works where the platform is already compatible. ## Links - [[3. Resources/Permanent Notes/A Contribution Pipeline Needs a Defined Next Step After Training]] — because contrasts; that note is about a program losing people after onboarding ends, this one is about a tool retaining people by never making them redo onboarding at all. - [[3. Resources/MOCs/DevRel MOC]] — because applies-in; detect-and-extend installers are a recurring developer-experience lever for adoption metrics. - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — because evidence-for; a concrete case of AI agent tooling integrating into, not replacing, an existing developer workflow. ## Tests / falsifiers - Compare install-completion rates for a detect-and-extend installer vs. a from-scratch setup requirement, holding the underlying tool constant. - Find a counter-case where a "detect and extend" installer actually increased friction (e.g. by silently conflicting with an existing config) — would bound the claim's scope further. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/WordPress Studio + MCP - A Better AI Workflow]] — states the installer's detect-and-extend design directly.