Skip to content

APM Framework v4.0.2 - Critical Plopdock Hook Integration Fix

Choose a tag to compare

View all tags
@omayhemo omayhemo released this 13 Aug 21:41
· 34 commits to master since this release
v4.0.2
818330f

🔧 APM Framework v4.0.2 - Critical Plopdock Hook Integration Fix

Critical Update: Fixed a major issue where agents were not properly forced to use Plopdock MCP for development server commands.

🚨 What Was Fixed

The Problem: In v4.0.1, when users enabled Plopdock MCP during installation, agents could still run development server commands directly (like npm start, python manage.py runserver) instead of using the Plopdock MCP server for persistent management.

The Solution: The pre-tool hook now properly integrates Plopdock MCP interception logic, ensuring all development server commands are managed through the MCP server when enabled.

🔧 Fixed

  • CRITICAL: Pre-tool hook now properly integrates Plopdock MCP interception
  • Fixed agents not being forced to use Plopdock MCP for development server commands
  • Pre-tool hook now checks PLOPDOCK_MCP_ENABLED environment variable
  • Added bypass functionality with BYPASS_MCP=1 prefix
  • Fixed dashboard URL consistency (uses PLOPDOCK_MCP_URL environment variable)
  • Comprehensive development server command pattern matching (30+ patterns)

🚀 Improved

  • Enhanced pre-tool hook with integrated Plopdock interception logic
  • Better error handling and logging for MCP integration
  • Voice notifications for development server interception
  • Unified hook architecture eliminates need for separate Plopdock hook file

🛡️ Security

  • All development server commands now properly managed through Plopdock MCP
  • Prevents direct server execution when MCP integration is enabled
  • Maintains persistent server management across Claude Code sessions

🎯 Impact for Users

✅ After v4.0.2:

When agents try to run development server commands:

🚫 Direct server launch prevented - Using Plopdock MCP instead

Original command: npm start
Framework detected: React
Project: my-app

The Plopdock MCP server will manage this development server for you.
Benefits:
- Server persists across Claude Code sessions
- Real-time monitoring at http://localhost:8080
- Centralized log management
- Process lifecycle control

I'll use the MCP server:start tool instead to launch your server.
To bypass this interception, prefix your command with BYPASS_MCP=1

❌ Before v4.0.2:

Agents could run npm start directly, bypassing Plopdock MCP management.

🚀 Installation

Quick Install (30 seconds)

# Non-interactive installation with defaults
curl -fsSL https://raw.githubusercontent.com/omayhemo/APM/master/install.sh | bash -s -- --defaults

# Interactive installation
curl -fsSL https://raw.githubusercontent.com/omayhemo/APM/master/install.sh | bash

# With TTS voice notifications
curl -fsSL https://raw.githubusercontent.com/omayhemo/APM/master/install.sh | bash -s -- --with-tts --defaults

Manual Installation

# Download and extract
wget https://github.com/omayhemo/APM/releases/download/v4.0.2/apm-v4.0.2.tar.gz
tar -xzf apm-v4.0.2.tar.gz
cd apm-v4.0.2

# Install
./installer/install.sh

🛠️ Requirements

  • Claude Code (Claude Desktop CLI) - Required
  • Linux, macOS, or WSL
  • 2GB free space
  • Git (optional, for version control)

📚 Documentation

After installation, comprehensive documentation is available at:

  • .apm/README.md - Complete documentation index
  • .apm/documentation/ - All guides and references

⚡ Key Features

  • 4-8x Faster Development - Native parallel execution
  • 9 Expert AI Agents - Each specialized in their domain
  • 85+ Commands - Complete development lifecycle coverage
  • Zero Setup Time - Working team in under 5 minutes
  • Production Ready - Used by teams shipping real products
  • 🆕 Proper Plopdock Integration - Development servers managed persistently

Ready to revolutionize your development workflow? Install APM and experience the power of parallel AI agents working as your team with proper development server management.

Assets 3
Loading