v1.2.3

What's new

Skill output optimisation — reduced context growth

Verbose Composer, Drush, and Docker output is now filtered in the four heaviest skills, significantly reducing how fast the chat context grows during a work session:

• drupal-init: composer create-project, composer require, and drush site:install output trimmed to 3–5 lines each
• drupal-stack: docker compose up --build output trimmed to 8 lines
• drupal-install: composer require output trimmed to 5 lines
• drupal-analyze: PHPStan output 30→15 lines, PHPCS output 40→20 lines

The didactic 💡 blocks in learning mode are unaffected — they are generated by the agent independently of the raw command output.

v1.2.2

What's new

Usage & Performance panel improvements

• By Provider / Model — new breakdown table grouping turn history by provider+model, showing turn count, total tokens, average cache hit rate and cost per group
• Persistent Turn History — turn data now survives page refreshes (saved to localStorage, max 50 turns, accumulates across provider/model switches)
• Added Clear button to reset turn history manually

Fixes

• Fixed race condition in turn capture that silently dropped turns when agent response arrived mid-poll
• Fixed OOBE flow for externally-configured providers (e.g. local-claude): detects no-inputs card and fetches models directly, bypassing broken card flow
• Fixed TopBar not updating provider/model display after OOBE model selection
• Fixed drupal-status skill timeout on disk check step

v1.2.0 — Usage & Performance Panel

What's new

Usage & Performance tab

New dedicated panel (after Plans) with real-time token analytics powered by PiClaw's /agent/context endpoint:

• 4 stat cards — total tokens, session cost, agent turns, cache hit rate
• Token breakdown — stacked bar chart: cache reads / cache writes / output / fresh input
• Last turn detail — model, provider, per-token breakdown, cost per turn
• Cache Efficiency — visual bars + tokens avoided, reduction percentage
• Environmental Impact — CO₂ used, CO₂ avoided by cache, water used/saved, and tree equivalent (e.g. ≈ 1 tree for 30 days) — all with Lucide icons
• Cost Breakdown — total, per-turn average, per-1K tokens
• Turn History — accumulates last 20 turns in-session

Data is session-only (PiClaw totals since container start). Refreshes every 30s.

Update

docker compose pull && docker compose up -d

v1.1.2 — Preserve user skills on update

What's new

Fix: user skills preserved on container update

Previously, docker compose pull && docker compose up -d would overwrite all skills in the workspace, including any custom skills or modifications made by the user.

New behaviour: the entrypoint only copies built-in skills that don't yet exist in the workspace. Skills already present (whether custom or previously installed) are never overwritten.

• Custom skills created via the agent → always preserved
• Built-in skills already in workspace → preserved (not overwritten)
• New built-in skills added in future releases → copied on first startup

Updating

docker compose pull
docker compose up -d

v1.1.1 — Fix version update check

What's new

Fix: version update check removed (CSP limitation)

The automatic update check via GitHub API was blocked by PiClaw's Content Security Policy (connect-src 'self'), producing a console error on every page load.

Replaced with:

• Settings → Version now shows a "Check for updates" button that opens GitHub Releases in a new tab
• Update commands (docker compose pull + docker compose up -d) always visible in Settings

Updating

docker compose pull
docker compose up -d

v1.1.0 — Drupal auto-install & local dev config

What's new

drupal-init: automatic Drupal installation

When initialising a new project without a DB dump, DrupalClaw now installs Drupal automatically via drush site:install and shows the admin credentials at the end.

• Strong admin password generated (12 chars, mixed alphanumeric + special)
• If the stack is already running: installs immediately, shows URL + credentials
• If the stack is not running yet: saves credentials, shows the command to use after drupal-serve

settings.local.php — complete setup

• hash_salt now generated via openssl rand and included in settings.local.php
• No more manual step required to complete the Drupal settings

services.local.yml — Twig debug & null cache

New file created automatically with local development settings:

• Twig debug mode ON (debug: true, auto_reload: true, cache: false)
• HTTP cacheability debug headers enabled
• Null cache backend for development
• Referenced from settings.local.php via container_yamls
• Gitignored automatically alongside settings.local.php

Informative output

Step 7 now explains every file created and shows a clear summary:

📁 Configuration files:
   settings.php         → includes settings.local.php
   settings.local.php   → DB credentials, hash_salt, dev settings
   services.local.yml   → Twig debug ON, cache backend: null

🎉 Drupal installed!
   🌐 URL:       http://localhost:8085
   👤 Username:  admin
   🔑 Password:  xK9mP2nQ!3

Skill sync fix (from v1.0.0 hotfix)

workspace/.pi/skills/ removed from git — image is now the authoritative source. Entrypoint always overwrites skills on startup, preventing stale versions from git checkouts.

Updating

docker compose pull
docker compose up -d

v1.0.0 — Initial stable release

DrupalClaw v1.0.0

First stable release of DrupalClaw — a self-hosted, agent-first Drupal development workspace running entirely in Docker.

What's included

IDE & Chat

• Browser-based IDE with chat, terminal, editor, file browser, and Drupal dev panel
• Multi-LLM provider support (GitHub Copilot, OpenAI, Anthropic, and more)
• Real-time SSE streaming with live activity feed (tool calls, agent thoughts)
• Multi-session chat with rename, archive, and restore
• Markdown rendering, file attachments, slash command autocomplete

Drupal Tooling (18 skills)

• drupal-init — scaffold new project or clone from Git, with DB and files import
• drupal-serve / drupal-stack — full stack lifecycle (nginx + PHP-FPM + MariaDB/PostgreSQL/SQLite)
• drupal-module, drupal-install, drupal-cr, drupal-status, drupal-logs
• drupal-db-export, drupal-db-import, drupal-db-query
• drupal-analyze, drupal-fix, drupal-debug, drupal-perf

Flows & Plans

• Flows: automated multi-step workflows (skill, prompt, MCP) with manual or scheduled triggers
• Plans: structured task lists with execute and validate lifecycle

Agent Behaviour

• Learning / Expert interaction modes
• PICK widgets for inline choices
• Live activity feed during agent processing
• Auto-compact context management

Workspace Isolation

• Each workspace gets a unique UUID-based Docker Compose project name
• Multiple DrupalClaw instances can run side by side without conflict

Infrastructure

• Multi-platform Docker image (linux/amd64 + linux/arm64)
• Published to GHCR: ghcr.io/paulocarv/drupalclaw-project:latest
• Semantic versioning — pin with image: ghcr.io/paulocarv/drupalclaw-project:1.0.0
• In-app update notifications (Settings → Version)

Getting started

git clone https://github.com/PauloCarv/drupalclaw-project.git
cd drupalclaw-project/docker
docker compose up -d
# Open http://localhost:8090

Updating

docker compose pull
docker compose up -d

Your Drupal project, chat history, flows, plans, and provider credentials are stored in Docker volumes and are never affected by updates.