v0.2.4: Unified Project Root Configuration 🎯

🎉 Highlights

This release introduces Unified Project Root Configuration, significantly simplifying the onboarding experience for both CLI and MCP users. Say goodbye to complex multi-variable configurations and hello to intelligent auto-detection!

🚀 What's New

For CLI Users

# Just navigate to your project and run:
cd /path/to/your/project
vibe

# That's it! Auto-detection handles the rest 🎉

For MCP Users (Claude Desktop, Cline, etc.)

{
  "mcpServers": {
    "vibe-coder-mcp": {
      "command": "npx",
      "args": ["vibe-coder-mcp"],
      "env": {
        "VIBE_PROJECT_ROOT": "/path/to/your/project",
        "OPENROUTER_API_KEY": "your-api-key"
      }
    }
  }
}

📦 Installation

NPM Global Install

npm install -g vibe-coder-mcp@0.2.4

NPX Usage (No Install)

npx vibe-coder-mcp@0.2.4

🔥 Key Features

Unified Project Root Configuration

• Single Configuration Point: One VIBE_PROJECT_ROOT variable replaces multiple tool-specific variables
• Auto-Detection: CLI users get automatic project root detection - zero configuration needed!
• Transport Awareness: Different behavior based on runtime environment (CLI vs MCP)
• Backward Compatible: All legacy configurations continue to work

Enhanced Setup Wizard

• Interactive configuration with intelligent defaults
• Auto-detection toggle for zero-configuration usage
• Comprehensive validation before saving
• Improved user experience with clear prompts

Documentation Improvements

• Quick start guides for different user types
• Tool-specific documentation enhancements
• Troubleshooting section
• Migration guides from legacy configurations

📋 Full Changelog

Added

• Unified project root configuration system
• Auto-detection for CLI users
• Transport context awareness
• Enhanced setup wizard
• Comprehensive documentation updates

Changed

• Simplified environment variable structure
• Enhanced UnifiedSecurityConfigManager
• Improved CLI initialization sequence
• Updated all tool READMEs
• Refined configuration templates

Fixed

• CLI configuration persistence issues
• Version display problems
• Service initialization order
• Directory resolution edge cases
• Security boundary validation

Removed

• Redundant package-security-fix.sh script
• Outdated configuration complexity
• Unnecessary directory resolution duplication

🔄 Migration Guide

From v0.2.3 or Earlier

Your existing configurations will continue to work! However, we recommend migrating to the simplified approach:

Old Configuration (Multiple Variables):

CODE_MAP_ALLOWED_DIR="/path/to/project"
VIBE_TASK_MANAGER_READ_DIR="/path/to/project"
VIBE_TASK_MANAGER_WRITE_DIR="/path/to/project/output"
# ... and more

New Configuration (Single Variable):

VIBE_PROJECT_ROOT="/path/to/project"
# That's it! 🎉

🙏 Acknowledgments

Thanks to all contributors and users who provided feedback to improve the onboarding experience!

📚 Documentation

• README
• NPM Package
• Issues & Feedback

Full Release Notes: See RELEASE_NOTES_v0.2.4.md for detailed information.