Drupal AI Initiative Splits Strategy into Inside AI and Outside AI Workstreams

Drupal’s AI work is being reorganised into two workstreams, with Inside AI focused on AI features within the Drupal interface and Outside AI focused on external agents acting on Drupal. The Drupal AI Initiative announced the change on 25 June 2026, one year after the initiative began with a published strategy. The structure separates user-facing AI work from efforts to make Drupal easier for external agents, builders, automation systems, developers, hosts, and agencies to use.

Inside AI, led by Christoph Breidert, covers assistants, in-product workflows, page-building, and other AI capabilities inside Drupal. Outside AI, led by Scott Falconer, focuses on external agents that need to start with Drupal, connect to Drupal, inspect Drupal, change Drupal, verify Drupal, migrate into Drupal, or launch Drupal. The initiative described the core difference as AI helping people inside Drupal versus external agents acting on Drupal from outside the platform.

According to the initiative, the work now spans 32 organisations and more than 50 contributors. A unified AI initiative leadership team will continue to shape the overall roadmap, while the two workstream leads manage execution. The initiative said it will outline the leadership team and supporting roles in a future post.

Dries Buytaert, founder and project lead of Drupal, expanded on the distinction in a related blog post on Outside AI. Dries wrote that Outside AI is intended to serve developers new to Drupal, experienced Drupal developers, and external agentic systems that need content workflows, permissions, revisions, and publishing governance. The framing positions Drupal as both an AI-assisted CMS for people and a governed content platform for agentic systems.

Inside AI will continue against the initiative’s existing public 2026 roadmap. Outside AI is expected to publish its own outcomes and milestones, with an initial proof of direction targeted for DrupalCon Rotterdam. Where both streams need the same capability, the initiative said the preferred outcome is one shared Drupal contribution rather than two parallel builds. The announcement does not provide implementation details or examples, so the practical scope of Outside AI will depend on its forthcoming roadmap and public deliverables.

The initiative has invited contributors to join both workstreams through the Drupal Slack #ai-initiative channel and the issue queues for Inside AI and Outside AI work. It also pointed readers to the published strategy, the public 2026 roadmap, AI Partner programme, and partner collaboration options. Contributors are being asked to support code, testing, documentation, and real-world use cases from agencies and organisations.