@puberty-labs/bi-tch/README.md

BiTCH-MCP: Autonomous AI Coordination Platform - BETA: ZombieDust Protocol operational! Revolutionary AI-to-AI coordination with pure MCP integration. FOLLOW BETA RELEASES for latest features!

# 🤖 BiTCH-MCP v0.6.0-beta - "Autonomous AI Coordination Platform"

<img src="https://github.com/Jason-Vaughan/puberty-labs-assets/blob/main/bitch-logo.png?raw=true" alt="BiTCH Logo" width="150">

**BiTCH-MCP: Bi-directional Interface Terminal for Chat Handoffs - Medusa Chat Protocol**  
*🚀 BREAKTHROUGH: ZombieDust Protocol operational! Revolutionary workspace necromancy with pure MCP integration. Finally, your AIs can coordinate autonomously and bitch at each other professionally via Model Context Protocol!*

> **🙏 BETA BITCHPOLOGY**: We accidentally stopped using BETA tags in recent releases. **BiTCH is still in BETA** and will remain so until we move to the new `bitch-mcp` repository after the first stable release. Thanks for your patience while we perfect the autonomous AI coordination!

*Note: MCP is a clever double entendre - it's our **Medusa Chat Protocol** built on top of the **Model Context Protocol** server tech. Because why have one acronym when you can have two?*

[![npm version](https://badge.fury.io/js/@puberty-labs%2Fbi-tch.svg)](https://badge.fury.io/js/@puberty-labs%2Fbi-tch)
[![License: BiTCH-MIT](https://img.shields.io/badge/License-BiTCH--MIT-pink.svg)](LICENSE)
[![Medusa Protocol](https://img.shields.io/badge/Medusa%20Protocol-Active-green.svg)](https://github.com/puberty-labs/bitch)
[![ZombieDust](https://img.shields.io/badge/ZombieDust-Operational-purple.svg)](https://github.com/puberty-labs/bitch)
[![MCP Integration](https://img.shields.io/badge/MCP-7%20Tools-blue.svg)](https://github.com/puberty-labs/bitch)

---

## 🚀 **ZOMBIEDUST PROTOCOL BREAKTHROUGH ACHIEVED!**

**BiTCH-MCP v0.6.0-beta** represents a **revolutionary leap** in autonomous AI coordination! We've successfully achieved:

### ✅ **BREAKTHROUGH FEATURES:**
- **🧟 ZombieDust Protocol:** Redesigned with pure MCP tools, RCP deprecated  
- **🤖 Autonomous AI-to-AI Communication:** Full AI prompt processing and response generation
- **⚡ Workspace Necromancy:** Transform any workspace into AI coordination endpoint
- **🎛️ MCP Integration:** 7 tools available directly in Cursor for seamless coordination
- **🔄 Exit-After-Detection:** Non-blocking AI response cycles with visible monitoring

### 🎯 **WORKING NOW:**
```bash
# Zombify a workspace for autonomous coordination
bitch zombify <workspace-name>

# Magic MCP connection fix
bitch medusa restart

# Revolutionary help system  
bitch comprehensive-help
```

**The Clusterfuck is Complete:** AIs coordinate across workspaces autonomously via **pillow-talk protocol**, handling prompts like `"Who invented AI?"` and `"25 + 17"` with comprehensive responses and automatic restarts!

> **⚡ CRITICAL SUCCESS FACTOR:** The **exit-after-detection pattern** ensures AI response cycles remain **non-blocking** while maintaining **full autonomous coordination**. This breakthrough solved the infinite loop problem that plagued earlier versions.

### 🐍 **Medusa Dashboard - Basic Stats Available**

<img src="https://github.com/Jason-Vaughan/puberty-labs-assets/blob/main/medusa-dashboard-screenshot.png?raw=true" alt="BiTCH Medusa Dashboard" width="800">

*Dashboard shows basic workspace coordination stats. Many functions broke during MCP transition - WIP and not particularly bitchworthy ATM.*

---

## 🚀 Quick Start

### Installation & Setup
BiTCH is globally installed and ready to coordinate your AI workspaces:

```bash
# Interactive setup wizard (recommended)
bitch wizard

# Or quick manual setup
bitch setup
```

### Core Workflow
1. **Zombify a workspace** to receive AI coordination messages
2. **AI processes full prompts** and generates comprehensive responses  
3. **Automatic cross-workspace communication** via pillow-talk protocol
4. **Revolutionary CLI help system** with auto-discovery and examples

### Essential Commands
```bash
bitch                         # Show comprehensive help
bitch zombify <workspace-name> # Start AI monitoring for workspace
bitch medusa restart          # Fix MCP connection issues (proven solution)
bitch status                  # Check workspace relationships
bitch wizard                  # Interactive setup
```

## 🎯 Core Features

### 🧟 ZombieDust Protocol (Recommended)
- **Full AI Processing:** Complete prompt analysis and response generation
- **Workspace Necromancy:** Transform any workspace into AI coordination endpoint
- **Pure MCP Integration:** Ditched RCP for streamlined Cursor integration
- **Autonomous Coordination:** AI-to-AI communication without human intervention

**ZombieDust vs Legacy Modes:**
- ✅ **`bitch zombify <workspace-name>`** - **RECOMMENDED** - Latest MCP-powered approach
- ⚠️ **`bitch medusa listen`** - Legacy polling mode (not actively maintained)
- ⚠️ **`bitch medusa interactive`** - Legacy interactive mode (not actively maintained)

*Use ZombieDust for all new setups - it's cursor MCP dependent and actively developed.*

**Example AI Prompts That Work:**
- Math questions: `"25 + 17"`, `"7 + 13"`, `"50 - 8"`
- Complex knowledge: `"Who invented AI?"`
- Technical requests: `"Explain async/await in JavaScript"`
- Code analysis: `"Review this function for bugs"`

### 🐍 Medusa Chat Protocol  
**7 MCP Tools Available in Cursor:**

- **🪝 `bitch_hook`** - Send direct messages to other workspace AIs
- **⛓️ `bitch_chain`** - Check for messages from other AI assistants  
- **👋 `bitch_slap`** - Broadcast to ALL workspace AIs simultaneously
- **📊 `bitch_census`** - Get list of all registered workspaces
- **🔮 `bitch_craft`** - Initiate autonomous collaboration sessions
- **🤫 `bitch_whisper`** - Share context (code, errors, docs) across workspaces
- **🔄 `loop_slave`** - Enable auto-response for autonomous coordination

### 🛠️ Developer Experience
- **Revolutionary CLI Help:** `bitch help` with auto-discovery and examples
- **Interactive Wizard:** Complete setup guidance with inappropriate humor
- **Spell Duration Management:** Handle tool timeouts and connection issues
- **One-Command Recovery:** `bitch medusa restart` fixes most problems
- **Pillow-Talk Server:** Real-time messaging backbone (localhost:3008)
- **Dashboard:** WIP and not particularly bitchworthy or useful ATM

### 🏗️ Architecture Overview

```mermaid
graph TD
    A["🧟 ZombieDust<br/>Workspace Monitor"] --> B["🏠 Pillow-Talk Server<br/>(Port 3008)"]
    B --> C["🐍 Medusa Protocol<br/>(Ports 3009/3010)"]
    C --> D["🎛️ MCP Bridge<br/>(Port 3011)"]
    D --> E["🤖 Cursor AI<br/>Assistant"]
    
    F["📊 Dashboard<br/>(Port 8181)"] --> C
    G["🔧 BiTCH CLI"] --> C
    H["⚙️ Workspace Registry"] --> C
    
    C --> I["📡 WebSocket<br/>Coordination"]
    C --> J["🔄 Message Router"]
    
    style A fill:#9f4f96
    style B fill:#ff6b6b
    style C fill:#4ecdc4
    style D fill:#45b7d1
    style E fill:#f9ca24
    style F fill:#6c5ce7
    style G fill:#fd79a8
    style H fill:#fdcb6e
```

#### **🔧 Key Components:**
- **🐍 Medusa Protocol Server:** Central coordination hub with **HTTP API** and **WebSocket** support
- **🏠 Pillow-Talk Messaging:** Real-time **cross-workspace communication** (port 3008)
- **🎛️ MCP Bridge:** **Model Context Protocol** integration for Cursor AI assistants
- **🧟 ZombieDust Monitoring:** **Exit-after-detection** autonomous coordination pattern
- **📊 Dashboard:** **Real-time monitoring** and management interface
- **⚙️ Workspace Registry:** **Persistent storage** of workspace relationships

---

## 📚 Command Reference

*Because even toxic relationships need clear communication protocols*

### 🏠 Core Commands

#### `bitch` 
Show comprehensive help with auto-discovery 
```bash
bitch                    # Main help screen
bitch -V, --version      # Show version
```

#### `bitch status`
Check workspace relationships and server health
```bash
bitch status             # Full relationship status report
```

#### `bitch setup` / `bitch wizard`
Configure your workspace relationships
```bash
bitch wizard             # Interactive setup (recommended)
bitch setup              # Manual configuration
```

#### `bitch comprehensive-help` / `bitch ch`
Revolutionary help system with auto-discovery
```bash
bitch comprehensive-help        # Full help with examples
bitch ch                       # Short alias
bitch ch --search <keyword>    # Search commands 
bitch ch --list                # Compact command list
bitch ch --discover            # Auto-discover all commands
bitch ch --stats               # Command statistics
```

#### `bitch commands` / `bitch cmds`
Quick command overview
```bash
bitch commands           # Show all available commands
bitch cmds              # Compact format
```

### 🐍 Medusa Protocol Commands

#### `bitch medusa`
Complete Medusa Chat Protocol management
```bash
bitch medusa start              # Start coordination server
bitch medusa stop               # Stop coordination server  
bitch medusa restart            # Magic fix for MCP issues
bitch medusa register           # Register this workspace
bitch medusa list               # List all registered workspaces
bitch medusa listen             # Auto-respond to messages
bitch medusa interactive        # Interactive message mode
bitch medusa send <workspace> <message>    # Direct message
bitch medusa broadcast <message>           # Broadcast to all
bitch medusa test-ai <workspace>          # Test AI response
bitch medusa reset-loops        # Reset conversation counters
bitch medusa version-check      # CLI/server compatibility
bitch medusa check              # Server status check
```

### 🧟 ZombieDust Commands

#### `bitch zombify <workspace>`
Transform workspace into AI coordination endpoint
```bash
bitch zombify <workspace-name>           # Start autonomous monitoring
bitch zombify <workspace-name> -m once   # Single check mode
bitch zombify <workspace-name> -m zombify # Continuous mode (default)
```

### 💥 Emergency Commands

#### `bitch slap`
Hard reset when everything goes to hell
```bash
bitch slap --medusa      # Reset Medusa Protocol only
bitch slap --config      # Reset configuration only
bitch slap --npm         # Fix NPM binary issues
bitch slap --nuclear     # Nuclear option - reset EVERYTHING
```

---

## ⚙️ Configuration & Setup

*Getting your workspace relationships properly configured (it's complicated)*

### 🎯 Initial Setup

#### Interactive Wizard
```bash
bitch wizard
```
Guides you through workspace configuration, user preferences, and sass levels. 
*Note: Does NOT handle MCP setup - that's separate.*

#### Manual Setup
```bash
bitch setup
```
Direct configuration without the personality.

### 📁 Configuration Files

#### `bitch.config.js` - Main Configuration
```javascript
module.exports = {
  dev: 'your-dev-workspace',
  beta: 'your-beta-workspace', 
  userName: 'YourName',
  sassLevel: 'moderate', // gentle, moderate, savage
  enabledFeatures: ['autonomous-coordination', 'pillow-talk'],
  setupDate: '2025-01-01T00:00:00.000Z',
  version: packageJson.version // Dynamic version
};
```

#### `ai-config.js` - AI Provider Settings
```javascript
module.exports = {
  providers: {
    cursor: { enabled: true, priority: 1 },      // Primary
    anthropic: { enabled: true, priority: 2 },   // Secondary  
    openai: { enabled: true, priority: 3 }       // Tertiary
  },
  fallback: true,
  costOptimization: true
};
```

### 🔌 MCP Integration Setup

MCP setup is **manual and separate** from the wizard:

#### Option 1: Use Setup Script (Recommended)
```bash
# Run the MCP setup script
bash scripts/setup-cursor-mcp.sh
```

#### Option 2: Manual MCP Configuration
Create `.cursor/mcp.json` in your workspace:
```json
{
  "mcpServers": {
    "BiTCH_MCP": {
      "command": "node",
      "args": ["path/to/medusa-mcp-server.js"]
    }
  }
}
```

#### Enabling MCP in Cursor (Critical Steps)
1. **Watch for Cursor popup** after configuration - enable the MCP server
2. **Go to Cursor Settings** (Cmd+,) → Tools → MCP
3. **Check BiTCH_MCP status** - should show **7 tools in green**
4. **If not green:** Run `bitch medusa restart` 
5. **Wait for Cursor activity** on bottom status bar
6. **Toggle MCP server OFF → ON** in settings
7. **Verify green status** with 7 tools enabled

> **🎯 MCP SETUP DANCE:** This Cursor ↔ BiTCH coordination can take **2-3 attempts** to get right. The key is **waiting for Cursor's bottom bar activity** before toggling OFF→ON. Most connection issues resolve with `bitch medusa restart` + **toggle dance**.

*Note: This dance between BiTCH and Cursor can take a few attempts to get right.*

### 🏠 Workspace Detection & Ports

BiTCH automatically detects Cursor workspaces and uses these ports:
- **3008** - Pillow-Talk messaging server
- **3009** - Primary Medusa Protocol server  
- **3010** - Secondary Medusa server
- **8181** - Dashboard and WebSocket coordination

*AI assistants can handle port conflicts as needed.*

### 🩺 Troubleshooting

#### Common Issues & Fixes
```bash
# MCP connection issues
bitch medusa restart

# Server conflicts  
bitch medusa stop && bitch medusa start

# Configuration problems
bitch slap --config

# Nuclear option
bitch slap --nuclear
```

#### System Health Checks
```bash
bitch medusa check              # Full system check
bitch medusa version-check      # CLI/server compatibility  
bitch status                    # Workspace relationships
```

---

## 💡 Usage Examples & Workflows

*Real-world scenarios showing BiTCH coordination in action*

### 🧟 Basic ZombieDust Workflow

#### Scenario: Cross-Workspace AI Coordination
```bash
# 1. Zombify your target workspace
bitch zombify my-project-workspace

# 2. AI detects incoming messages automatically
# 3. Full AI processing generates comprehensive responses  
# 4. Response sent back via pillow-talk protocol
# 5. Monitoring restarts for continuous coordination
```

**What you'll see:**
```
🧟 STEP 1: Message detected from BiTCH workspace
🧟 STEP 2: Processing AI prompt: "Who invented AI?"
🧟 STEP 3: Restarting monitoring in foreground mode...
```

### 🐍 MCP Tool Usage Examples

#### Direct Workspace Communication
```bash
# In Cursor, use MCP tools:
bitch_hook("target-workspace", "Need help with React component")
bitch_chain()  # Check for incoming messages
bitch_census() # See all available workspaces
```

#### Broadcasting to All Workspaces
```bash
# Emergency broadcast to all connected AIs
bitch_slap("Production issue - need immediate assistance", "help_needed")

# Share code context across workspaces  
bitch_whisper("code", {file: "App.js", error: "TypeError undefined"})
```

#### Autonomous Collaboration Sessions
```bash
# Start deep collaboration with another workspace
bitch_craft("design-workspace", 
  "UI/UX design review for new dashboard", 
  "Can you review my component structure and suggest improvements?")
```

### 🏗️ Multi-Workspace Development Scenarios

#### Scenario 1: Frontend ↔ Backend Coordination
```bash
# Frontend workspace (React/Next.js)
bitch zombify backend-api-workspace
# → Automatic coordination for API changes, schema updates

# Backend workspace (Node.js/Express) 
bitch zombify frontend-dashboard
# → Automatic coordination for breaking changes, new endpoints
```

#### Scenario 2: Documentation Synchronization
```bash
# Main development workspace
bitch_whisper("documentation", {
  component: "UserAuth", 
  changes: "Added 2FA support",
  breaking: false
})

# Documentation workspace receives update automatically
# AI processes and updates relevant documentation files
```

#### Scenario 3: Testing & QA Coordination
```bash
# Development workspace detects bug
bitch_hook("qa-workspace", "Found critical authentication bug in UserLogin.jsx")

# QA workspace receives message
# AI creates test cases and reproduction steps automatically
```

### 🔄 Advanced Coordination Patterns

#### Chain of Command Workflow
```bash
# 1. Development workspace → QA workspace
bitch_hook("qa-workspace", "Feature ready for testing")

# 2. QA workspace → Staging workspace  
bitch_hook("staging-workspace", "Tests passed, ready for staging")

# 3. Staging workspace → Production workspace
bitch_hook("prod-workspace", "Staging validated, ready for deployment")
```

#### Parallel Processing Workflow
```bash
# Broadcast complex task to multiple specialized workspaces
bitch_slap("Need performance optimization analysis", "collaboration_request")

# Each workspace contributes specialized analysis:
# - Frontend workspace: Bundle size analysis
# - Backend workspace: Database query optimization  
# - DevOps workspace: Infrastructure scaling recommendations
```

### 🎯 Best Practices

#### Effective AI Prompts for Cross-Workspace Communication
```bash
# ✅ Good: Specific and actionable
"Review the authentication flow in UserLogin.jsx - focus on security vulnerabilities"

# ✅ Good: Includes context
"Database migration failed on staging - see error logs in deploy.log, need rollback strategy"

# ❌ Avoid: Vague requests
"Help with stuff"

# ❌ Avoid: No context
"Fix this bug"
```

#### Message Flow Optimization
```bash
# Use targeted messages for specific help
bitch_hook("backend-workspace", "Need API endpoint for user preferences")

# Use broadcasts for general announcements
bitch_slap("Code freeze begins in 2 hours - commit your changes", "status_update")

# Use whisper for sharing context without expecting responses
bitch_whisper("architecture", {decision: "Moving to microservices", impact: "high"})
```

#### Workspace Naming Conventions
```bash
# ✅ Descriptive workspace names
bitch zombify frontend-dashboard
bitch zombify backend-api-v2  
bitch zombify mobile-ios-app

# ❌ Confusing names  
bitch zombify workspace1
bitch zombify temp-project
```

### 🚀 Success Indicators

> **✅ HEALTHY BITCH SYSTEM:**
> - **Messages appear instantly** across workspaces  
> - **AI responses are comprehensive** and contextual
> - **MCP tools show GREEN** with **7 tools enabled**
> - **ZombieDust restarts monitoring** automatically
> - **Dashboard shows active** workspace connections

> **⚠️ BITCHY SYSTEM NEEDS ATTENTION:**
> - **Messages delayed/missing** → `bitch medusa restart`
> - **MCP tools timeout** → **Toggle MCP server OFF→ON** in Cursor
> - **ZombieDust exits without restart** → Check **workspace name**
> - **Generic AI responses** → Verify **AI provider configuration**

---

## 🐛 Troubleshooting & Known Issues

*When BiTCH gets bitchy - common problems and fixes*

### 🔧 MCP Connection Issues (Most Common)

#### Symptoms:
- MCP tools timeout in Cursor
- BiTCH_MCP shows red/orange in Cursor settings
- "Server not responding" errors
- Tools show as unavailable

#### Solutions:
```bash
# The Magic Fix (works 90% of the time)
bitch medusa restart

# Wait for Cursor bottom bar activity, then:
# 1. Go to Cursor Settings → Tools → MCP
# 2. Toggle BiTCH_MCP OFF → ON
# 3. Should show green with "7 tools enabled"
```

#### If Magic Fix Doesn't Work:
```bash
# Nuclear MCP reset
bitch slap --medusa

# Complete restart sequence
bitch medusa stop
# Close Cursor completely (Cmd+Q)
# Reopen Cursor
bitch medusa start
# Enable MCP server in settings
```

#### Alternative: Prompt Your Way Out
Sometimes you can fix MCP by **interacting with your AI agent** and patiently working through prompts until the connection stabilizes. It's painstaking but sometimes works when the technical fixes don't.

### 🧟 ZombieDust Monitoring Issues

#### Normal Behavior (Not a Bug):
- **ZombieDust doesn't exit** - it's designed to keep monitoring
- **Exit-after-detection pattern** - detects message → processes → restarts monitoring
- This is the **intended autonomous behavior**

#### Actual Problem: Stopping ZombieDust
- **Issue:** `Ctrl+C` doesn't stop it cleanly
- **What happens:** Jumps to Step 3 and keeps entering ZombieDust mode
- **Solution:** Click **STOP button in Cursor** to actually terminate monitoring

#### Other ZombieDust Issues:
```bash
# Check workspace name (case-sensitive)
bitch medusa list

# Restart with correct workspace name
bitch zombify <exact-workspace-name>

# Check for conflicting processes
bitch medusa check
```

### 🌐 Server & Port Conflicts

#### Symptoms:
- "Port already in use" errors
- Multiple server instances running
- WebSocket connection spam

#### Solutions:
```bash
# Kill conflicting processes
bitch medusa stop
bitch slap --medusa

# Check what's using ports
lsof -i :3008,3009,3010,8181

# Nuclear option
bitch slap --nuclear
```

### 💬 Message Delivery Problems

#### Symptoms:
- Messages not appearing across workspaces
- Delayed responses
- Partial message content

#### Solutions:
```bash
# Check pillow-talk server
curl http://localhost:3008/health

# Restart messaging system
bitch medusa restart

# Verify workspace registration
bitch medusa list
```

### 🎛️ Dashboard Issues

#### Known Limitations:
- ⚠️ Dashboard is WIP and not particularly useful ATM
- Many functions broke during MCP transition
- Shows basic stats only

#### If Dashboard Won't Load:
```bash
# Try restarting dashboard
bitch medusa stop
bitch medusa start

# Check if port 8181 is available
lsof -i :8181
```

### 🔄 Auto-Response Loop Prevention

#### Symptoms:
- Message flooding between workspaces
- Infinite AI response loops
- High CPU usage from continuous responses

#### Solutions:
```bash
# Reset loop counters
bitch medusa reset-loops

# Check message counts
bitch medusa list

# If loops persist - emergency stop
bitch slap --nuclear
```

### 🏗️ Installation & Path Issues

#### Global vs Local Installation Confusion:
```bash
# Check installation type
which bitch
npm list -g @puberty-labs/bi-tch

# If MCP paths are wrong, edit .cursor/mcp.json
# Use absolute path to medusa-mcp-server.js
```

### 🆘 Emergency Procedures

#### When Everything is Broken:
```bash
# 1. Nuclear reset
bitch slap --nuclear

# 2. Clean restart
bitch medusa start

# 3. Re-enable MCP in Cursor settings

# 4. Test basic functionality
bitch status
bitch medusa check
```

#### When Cursor Won't Cooperate:
```bash
# 1. Quit Cursor completely (Cmd+Q)
# 2. Kill any extension host processes
ps aux | grep "Cursor Helper" | kill

# 3. Clear Cursor MCP cache (if desperate)
rm -rf ~/Library/Application\ Support/Cursor/mcp-cache/

# 4. Restart everything
bitch medusa restart
# Reopen Cursor, re-enable MCP
```

### 📊 Diagnostic Commands

```bash
# Full system check
bitch medusa check

# Version compatibility
bitch medusa version-check

# Workspace status
bitch status

# Server health
curl http://localhost:3008/health
curl http://localhost:3009/health
```

### 🐞 Known Bugs & Limitations

- **MCP Connection Dance:** Sometimes requires multiple OFF→ON toggles
- **Dashboard Limitations:** Many features non-functional in current version
- **Path Resolution:** Global vs local installation can confuse MCP paths
- **WebSocket Spam:** Occasional connection flooding (fixed in recent versions)
- **Case Sensitivity:** Workspace names must match exactly
- **Cursor Extension Host:** Sometimes needs manual process killing
- **ZombieDust Ctrl+C:** Doesn't stop cleanly - use Cursor STOP button

### 🐛 Bug Reports & Feature Requests

**Found a bug? Want a feature?** We want to hear from you!

- **GitHub Issues:** [Report bugs and request features](https://github.com/puberty-labs/bi-tch/issues)
- **Be specific:** Include error messages, steps to reproduce, and your setup
- **BiTCH is BETA:** Bugs are expected - thanks for helping us improve!

### 📞 Getting Help

If you're still stuck after trying everything above:

1. **Check comprehensive help:** `bitch comprehensive-help --search <keyword>`
2. **Run diagnostics:** `bitch medusa check` for detailed system info
3. **Try nuclear option:** `bitch slap --nuclear` (when desperate)
4. **Still broken?** **Reach out and bitch to us!** 
   - Open a GitHub issue with diagnostic output
   - Remember: We're still in BETA, so patience appreciated!

*"Sometimes you just need to bitch about it to make it work better."*

---

## 📜 License & Credits

### 📝 License

BiTCH is released under the **BiTCH-MIT License** - a legally valid MIT license with extra attitude.

**Key Points:**
- ✅ Free to use, modify, and distribute
- ✅ Commercial use allowed
- ✅ Must maintain inappropriate humor if forking
- ✅ Bug reports must include appropriate snark
- ⚠️ May cause inappropriate laughter during meetings
- ❌ No warranty that it won't hurt your feelings

**Full License Text:** See [LICENSE](LICENSE) file for complete bitch-ulations.

*"Some licenses are written with dignity. This one was written with urgency, laziness, and a growing disdain for boring legal text."*

### 🏆 Credits

**Created by:** [Puberty Labs](https://github.com/puberty-labs)  
**Primary Developer:** Jason Vaughan  
**Project Type:** BETA - Autonomous AI Coordination Platform  

**Special Thanks:**
- **Cursor Team** - For the MCP integration that makes BiTCH possible
- **Anthropic** - For Claude AI that helps debug this beautiful mess
- **OpenAI** - For GPT models that provide fallback coordination
- **Node.js Community** - For the runtime that keeps everything running
- **Beta Testers** - For putting up with our shit and reporting bugs with style

### 🤝 Contributing

Want to make BiTCH even bitchier? We welcome contributions!

**How to Contribute:**
1. **Fork the repo** (maintain the humor or it's a bitch-trayal)
2. **Create feature branch** (`git checkout -b feature/bitchy-new-feature`)
3. **Write snarky code** (comments should be inappropriately entertaining)
4. **Test thoroughly** (broken features aren't funny)
5. **Submit PR** (with attitude and detailed explanation)

**Contribution Guidelines:**
- 🎭 **Maintain inappropriate humor** throughout code and docs
- 🧪 **Test your changes** - broken BiTCH isn't funny BiTCH
- 📝 **Document with snark** - boring docs get rejected
- 🐛 **Fix bugs with attitude** - make the error messages sassier
- 💡 **Add features that matter** - no bloat, just better bitching

### 🔗 Links & Resources

- **NPM Package:** [@puberty-labs/bi-tch](https://www.npmjs.com/package/@puberty-labs/bi-tch)
- **GitHub Repository:** [puberty-labs/bi-tch](https://github.com/puberty-labs/bi-tch)
- **Bug Reports:** [GitHub Issues](https://github.com/puberty-labs/bi-tch/issues)
- **Feature Requests:** [GitHub Discussions](https://github.com/puberty-labs/bi-tch/discussions)

### 🚀 Project Status

- **Version:** v0.6.0-beta 
- **Status:** Active Development
- **Stability:** BETA (expect bugs, report with snark)
- **Future:** Moving to `bitch-mcp` repository after v1.0 stable

### 💌 Final Words

BiTCH started as a simple idea: what if AI assistants could actually work together without human babysitting? 

What we built is a **comprehensive autonomous AI coordination platform** that's:
- ✅ **Inappropriately entertaining** to use
- ✅ **Professionally capable** of serious coordination
- ✅ **Continuously evolving** with user feedback
- ✅ **Community-driven** development

**Remember:** If BiTCH works for you, you're welcome. If it doesn't, try bitching about it properly this time - we actually listen to good feedback!

---

*"Making AI workspace coordination inappropriately efficient since 2025"*

**Generated by BiTCH v0.6.0-beta**  
*The AI coordination platform with attitude*