VibeWatch
Your AI pair programmer's eyes on your terminal
What is VibeWatch?
VibeWatch is a CLI tool that monitors your development commands and exposes terminal output to Claude (or any MCP-compatible AI assistant) in real-time. No more copy-pasting errors - just tell Claude "check my terminal" and it sees everything.
Quick Start
Then ask Claude: "I'm getting an error, check my terminal" - Claude automatically sees your terminal output via MCP.
Installation
Option 1: Global Install
Option 2: npx (no install)
Option 3: Local Development
Usage
Basic Usage
Wrap any command with vibewatch:
CLI Options
Examples
MCP Integration
Claude Desktop / Cursor Configuration
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json) or Cursor MCP settings:
Or if installed globally (npm install -g vibewatch):
Available MCP Tools
Tool | Description |
| Get recent terminal output with optional filtering |
| Get detailed crash information with stack traces |
| Quick view of recent errors only |
| Test connectivity |
MCP Tool Parameters
get_terminal_output:
get_crash_context:
API Endpoints
VibeWatch exposes a local HTTP API for direct queries:
Endpoint | Description |
| Server status and buffer stats |
| Recent output with progressive disclosure |
| Crash snapshot (if crashed) |
| Errors only |
| Errors with surrounding context |
Progressive Disclosure
Save tokens by requesting only what you need:
Features
Framework Detection
VibeWatch automatically detects and optimizes for:
JavaScript: Next.js, Vite, Webpack
Python: Django, FastAPI, pytest
General: Node.js, Python, Rust, Go
Smart Filtering
ANSI code stripping
Noise reduction (progress bars, HMR updates)
Repeated line collapsing
Stack trace filtering (node_modules/site-packages hidden by default)
Error Detection
Language-aware error pattern matching
Framework-specific error patterns
Non-fatal error notifications
Relevant file path extraction
Crash Handling
Automatic crash detection
Buffer snapshot preservation
Keep-alive mode for post-crash MCP queries
Exit code and signal reporting
Architecture
Development
Documentation
Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines.
Quick Contribution Guide
Fork the repository
Create a feature branch:
git checkout -b feature/amazing-featureMake your changes
Run tests:
npm testCommit:
git commit -m 'Add amazing feature'Push:
git push origin feature/amazing-featureOpen a Pull Request
Support
GitHub Issues - Bug reports & feature requests
Discussions - Questions & ideas
License
MIT - see LICENSE for details.
Built with love for the vibe coding community.