A comprehensive AI-powered development toolkit featuring live session logging, real-time constraint monitoring, semantic knowledge management, and multi-agent analysis β supporting both Claude Code and GitHub CoPilot.
# Install the system (safe - prompts before any system changes)
./install.sh
# Start Claude Code with all features
coding
# Or use specific agent
coding --claude
coding --copilot
# Query local LLM from command line (Docker Model Runner)
llm "Explain this error message"
cat file.js | llm "Review this code"For containerized deployment with persistent services:
# Switch to Docker mode (safe transition with health monitoring)
coding --switch-to-docker
# Start Claude - Docker services are already running
coding --claude
# Check current mode
coding --mode-statusThe transition system ensures safe mode switching with:
- Automatic pause of health monitors during transition
- Graceful service shutdown with data flush
- Automatic rollback on failure
- Multi-session support
- Docker-aware health verification (CGR cache, service restarts)
Benefits: Persistent MCP servers, shared browser automation across sessions, isolated database containers.
MCP Configuration: Automatically selects the correct MCP config based on deployment mode:
- Docker mode: Uses stdio-proxy β SSE bridge to communicate with containerized servers
- Native mode: Runs MCP servers directly as Node.js processes
- Configuration selection is centralized in
claude-mcp-launcher.sh
Health System Adaptation: The health verifier automatically detects Docker mode and adapts:
- CGR cache staleness uses
cache-metadata.jsonfallback (no.gitaccess) - Service restarts use Docker-appropriate commands
- Dashboard shows cached commit info instead of staleness count
To switch back to native mode:
coding --switch-to-nativeThe Docker stack runs 4 containers (coding-services, Qdrant, Memgraph, Redis) with 8 internal services managed by supervisord, using ~1.75 GB memory total.
See Architecture Report for full system overview, Docker Mode Transition for switching details, and Docker Deployment Guide for container configuration.
The installer follows a non-intrusive policy - it will NEVER modify system tools without explicit consent:
- Confirmation prompts before installing any system packages (Node.js, Python, jq)
- Skip options:
y(approve),N(skip),skip-all(skip all system changes) - Shell config backup with timestamped files before any modifications
- Syntax verification after shell config changes
Next Steps: Getting Started Guide
- π₯ Health System - Real-time monitoring, auto-healing, and status line indicators
- π Live Session Logging - Real-time conversation classification and routing
- π‘οΈ Constraint Monitoring - PreToolUse hook enforcement for code quality
- π§ Knowledge Management - Capture, visualize, and share development insights
- π Trajectory Generation - Automated project analysis and documentation
- π€ Multi-Agent Analysis - 11 specialized AI agents for comprehensive code analysis
- Claude Code - Full MCP server integration
- GitHub CoPilot - Enhanced VSCode integration with fallback services
- Agent-Agnostic - Same features regardless of AI assistant
- Docker Support - Containerized deployment with HTTP/SSE transport for MCP servers
Automatic health monitoring and self-healing with real-time dashboard
- Pre-prompt health verification with 3-layer resilience
- Auto-healing failed services (Docker-aware)
- Dashboard at
http://localhost:3032 - Service supervision hierarchy ensures services stay running
- π Status Line System - Real-time indicators in Claude Code status bar
Real-time conversation classification and routing with security redaction
- 5-layer classification system
- Multi-project support with foreign session tracking
- 98.3% security effectiveness
- Zero data loss architecture
Real-time development state tracking and comprehensive project analysis
- AI-powered activity classification (exploring, implementing, verifying, etc.)
- Status line integration
- Automated project capability documentation
Real-time code quality enforcement through PreToolUse hooks
- 18 active constraints (security, architecture, code quality, PlantUML, documentation)
- Severity-based enforcement (CRITICAL/ERROR blocks, WARNING/INFO allows)
- Dashboard monitoring at
http://localhost:3030 - Compliance scoring (0-10 scale)
Two Complementary Approaches for knowledge capture and retrieval:
- Manual/Batch (UKB): Git analysis and interactive capture for team sharing
- Online (Continuous Learning): Real-time session learning with semantic search
- Visualization (VKB): Web-based graph visualization at
http://localhost:8080 - Ontology Classification: 4-layer classification pipeline
- System Health Dashboard - Real-time health visualization
- MCP Constraint Monitor - PreToolUse hook enforcement
- MCP Semantic Analysis - 11-agent AI analysis system
- VKB Visualizer - Knowledge graph visualization
- Serena MCP - Structure-aware code search
- All Integrations - Complete integration list
- Installation & Setup - Complete installation guide
- Provider Configuration - LLM provider setup
- Troubleshooting - Common issues and solutions
Real-time conversation classification and routing with enterprise-grade security:
- 3-Layer Classification: Path analysis β Keyword matching β Semantic analysis
- 98.3% Security Effectiveness: Enhanced redaction with bypass protection
- Multi-User Support: Secure user isolation with SHA-256 hash generation
- Zero Data Loss: Every exchange properly classified and preserved
- 200x Performance: Optimized bulk processing with sub-millisecond tracking
Status: β Production Ready
PreToolUse hook integration for real-time code quality enforcement:
- 18 Active Constraints: Security, architecture, code quality, PlantUML, documentation
- Severity-Based: CRITICAL/ERROR blocks, WARNING/INFO allows with feedback
- Dashboard Monitoring: Live violation feed (port 3030)
- REST API: Programmatic access (port 3031)
- Testing Framework: Automated and interactive constraint testing
Status: β Production Ready
Capture, organize, and visualize development insights with git-based team collaboration:
- UKB (Update Knowledge Base): Auto git analysis + interactive capture
- VKB (Visualize Knowledge Base): Web-based graph visualization
- Graph Database: Agent-agnostic persistent storage (Graphology + Level)
- Git-Tracked JSON: Team collaboration via pretty JSON exports
- graph-sync CLI: Manual export/import/status operations
- Auto-Sync: Import on startup, export on changes (5s debounce)
- Team Isolation: Multi-team support with conflict resolution
- Domain-Specific: Automatic domain knowledge bases per team
Status: β Production Ready
11 specialized agents for comprehensive code analysis:
- CoordinatorAgent - Workflow orchestration
- GitHistoryAgent - Git commits and architectural decisions
- VibeHistoryAgent - Conversation file processing
- SemanticAnalysisAgent - Deep code analysis (uses LLM)
- WebSearchAgent - External pattern research
- InsightGenerationAgent - Insight generation with PlantUML (uses LLM)
- ObservationGenerationAgent - Structured UKB-compatible observations
- QualityAssuranceAgent - Output validation with auto-correction (uses LLM)
- ContentValidationAgent - Stale entity detection and knowledge refresh
- PersistenceAgent - Knowledge base persistence
- DeduplicationAgent - Semantic duplicate detection
Debug Mode: Full debugging support with single-step execution, substep inspection, and mock LLM mode for cost-free testing. See UKB Workflow System.
Status: β Production Ready
# Start visualization server
vkb
# View at http://localhost:8080
# Manual sync operations
graph-sync status # View sync status
graph-sync export # Export all teams to JSON
graph-sync import # Import all teams from JSON
graph-sync sync # Full bidirectional sync# Start dashboard (automatic with install)
cd integrations/mcp-constraint-monitor
npm run dashboard # http://localhost:3030
# API access
curl http://localhost:3031/api/status
curl http://localhost:3031/api/violations# Automatic during Claude Code sessions
# Session files in .specstory/history/
# Status line shows:
ππ 2130-2230(3min) βcoding
# π = logging, π = window closing, βcoding = activity detectedClaude Code:
# Repository analysis workflow
start_workflow {
"workflowType": "repository-analysis",
"parameters": {
"repository": ".",
"depth": 25,
"significanceThreshold": 6
}
}
VSCode CoPilot:
# Via HTTP API
curl -X POST http://localhost:8765/api/semantic/analyze-repository \
-H "Content-Type: application/json" \
-d '{"repository": ".", "depth": 25}'# Set API keys
export ANTHROPIC_API_KEY="your-key-here"
export OPENAI_API_KEY="optional-fallback"
# Configure preferred agent
export CODING_AGENT="claude" # or "copilot"See Getting Started for:
- API key setup
- MCP configuration
- Network setup (proxies/firewalls)
- Verification steps
# Test all components (check-only mode - safe, no modifications)
./scripts/test-coding.sh
# Interactive mode - prompts before each repair
./scripts/test-coding.sh --interactive
# Auto-repair mode - fixes coding-internal issues only
./scripts/test-coding.sh --auto-repair
# Check MCP servers
cd integrations/mcp-server-semantic-analysis && npm test
# Check constraint monitor
cd integrations/mcp-constraint-monitor && npm testNote: The test script defaults to --check-only mode and will NEVER auto-install system packages.
β Health System - 4-layer monitoring with auto-healing β Live Session Logging - Real-time classification with 98.3% security β Constraint Monitoring - 18 active constraints with PreToolUse hooks β Knowledge Management - UKB/VKB with MCP integration β Multi-Agent Analysis - 11 agents with workflow orchestration β Status Line System - Real-time indicators in Claude Code status bar β Cross-Platform - macOS, Linux, Windows support
This is a personal development toolkit. For issues or suggestions:
- Check Troubleshooting
- Review Architecture Documentation
- Create an issue with detailed information
This project is licensed under the MIT License - see the LICENSE file for details.
Copyright Β© 2025 Frank Wornle
- Documentation Hub: docs/README.md
- Installation Guide: docs/getting-started.md
- LLM Providers & Local Models: docs/provider-configuration.md
- Docker Architecture: docs/architecture-report.md
- Docker Mode Transition: docs/docker-mode-transition.md
- Docker Deployment: docker/README.md
- System Overview: docs/system-overview.md
- Core Systems: docs/core-systems/
- Integrations: docs/integrations/
- Knowledge Management: docs/knowledge-management/


