Site Agent

Site Agent adds a chat panel to the Drupal administration interface. A signed-in user asks for a change in plain language, and a model, called through the AI module, makes it with Tool API tools. Each call runs as that user, with that user's permissions. Every call is recorded, and a change visitors would see waits for approval or for publishing.

Features

• Toolsets. Each toolset is a set of tools with its own permission, an approval mode per tool, limits on tool inputs and instructions for the model. Two ship with the module:
  • Editor: finds, reads and edits content and media, as drafts. It changes no structure.
  • Site builder: everything in Editor, plus content types, fields, form and view displays, menus, blocks, role permissions, Views edits and clones, URL alias patterns and image styles, where configuration is writable.
• Approvals. A tool runs without asking, asks once per conversation, or asks every time. Destructive tools, unclassified tools and content writes that go live at once always ask. A call the user couldn't make is refused before anyone is asked to approve it. Tools that send email or assign roles are left out of both toolsets, since content the model reads can carry instructions.
• Cards. An approval card shows a change before it runs: for content, each field by its label, rendered before and after; for configuration, a YAML diff against active configuration. A draft's card offers Publish to accounts the site's workflow allows.
• Audit log. Every call leaves a record, pre-approved calls included: the tool, its arguments, who decided, when, and the outcome.
• Configuration from git. Structure tools run only where configuration is writable, as decided by Config Read-only or a settings key. The panel lists each configuration item a conversation changed, with its diff against the sync directory and the command that exports it.
• Site context. With AI Context, the model follows the voice, standards and rules the site's editors publish there. Each toolset is an AI Context consumer: its items go into the system prompt, selected for the page the chat was opened on, and the model looks up the items for a page before it drafts or rewrites one, such as the rules for a content type or a section of the site.
• Models. The site chooses a model with tool calling from any provider the AI module has. It can let users pick one per chat from a list it limits, and, with AI Effort, set how much effort the model spends.
• Content Deployment. With Content Deployment, page edits go through its content spec tools and land as drafts without a prompt. On a development site, a conversation's content goes into the workspace that was active when it started, configuration is written outside any workspace, and the panel links to the workspace's changeset export.

Submodules

• Site Agent Tool Belt: Tool API tools for form and view display placement, menus, role permissions, block placement, recent log messages, and Views edits and clones. It depends on Tool API and core only.
• Site Agent Pathauto: Tool API tools to list and set Pathauto patterns.
• Site Agent AI Context: gives the model the site's AI Context items, in the system prompt and through a tool for the page being drafted. Installing it adds that tool to the toolsets that write content.
• Site Agent MCP: offers an account's toolset to remote MCP clients, such as Claude, through MCP Server, with the same checks, approvals and audit log as the chat. With MCP Server OAuth, clients sign in with OAuth.

Requirements

• Drupal 11.3 or later, and PHP 8.3.
• AI 1.5 or later, with a provider module that returns streamed tool calls, such as Anthropic or OpenRouter.
• Tool API 1.0 beta.
• The shipped toolsets use Tool Belt's tools, or Content Deployment's where it is installed. Drafts need Content Moderation or revisionable content.
• Optional: AI Context 1.0.0-rc1 or later for Site Agent AI Context, and MCP Server 2.0.0-beta5 or later for Site Agent MCP.

Installation

Tool API has no stable release yet, so the site's root composer.json must allow its stability:

composer require drupal/site_agent "drupal/tool:^1.0@beta"

Enable the module, choose a model at /admin/config/ai/site-agent/settings, and grant use editor toolset or use site_builder toolset to the roles that should have the panel.

For site context, enable Site Agent AI Context, grant "Use Published AI Context in AI Features" to the same roles, and publish context items in AI Context. Each toolset's subscriptions and limits are set on AI Context's consumers page.

Project status

Releases stay alpha or beta until Tool API reaches 1.0, since its APIs can still change between betas. The submodules are experimental for the same reason.

Similar projects

AI Agents runs agents on the AI module. Site Agent's approval contract follows its per-tool approval proposal, #3586020. Its runner sits behind an interface so it can be swapped for the runner AI 2.0 plans to move into AI core.