Skip to main content
The Drupal plugin participates in core component workflows. For local development, enable dev mode with sitectl set; it writes the override immediately:
Dev mode keeps the stack in the normal Compose model while adding the bind mounts expected for local custom module and theme work. It also persists composer.json and composer.lock from the Drupal container to the host, which is required when using sitectl drupal composer require, remove, or update to author dependency changes. Use ordinary git commands in the project checkout for branch, remote, and upstream management. To work through a sandboxed coding agent, add the assistant service:
The Drupal plugin supplies the Drupal-specific code mounts; the shared dev-mode component supplies the cli-sandbox service. The assistant defaults to --egress-profile interactive for trusted local development. The LibOps platform controller instead uses --egress-profile managed with the site’s literal private model-gateway IPv4 URL. Managed Task Agents must not receive --compose-access or --skip-egress-firewall. Disable dev mode the same way: