Coditect AI IDE - Multi-llm Browser IDE
Browser-Based IDE with Local llm Support, Multi-Agent Architecture, and Real-Time Collaboration
π§ͺ Testing Infrastructureβ
Latest: 2025-10-28 - Build #18 SUCCESS - Permission Fix Deployed β OPERATIONAL
Status Report: 2025-10-28T00:50:00Z - Complete Project Status π
MVP Scaling: 2025-10-27 - Scaling Analysis for 20 Users π
π Architecture Evolution (2025-10-27)β
Comprehensive documentation of design evolution:
β ADR-028: theia IDE Integration Evolution
- Why we adopted Eclipse theia instead of building a custom IDE
- 9-10 months time savings, $225K cost savings, 3x more features at MVP
- 68 theia packages, custom branding, VS Code extension compatibility
- Future roadmap: MCP integration, multi-llm chat panel
β ADR-029: StatefulSet Persistent Storage Migration
- Solved critical data loss problem with persistent volumes
- Migration from Deployment β StatefulSet with PVCs
- 100 GB workspace + 10 GB config per user
- Capacity planning for 10-20 β 50-100 β 500+ users
β Hybrid Storage Architecture (ADR-028 Part 1, Part 2) (2025-10-28)
- Cost Optimization: 96% savings vs NFS ($7/user vs $205/user)
- Hybrid Approach: Shared base (Docker layers) + user-specific PVCs (10 GB)
- Performance: <1ms latency with GCE Persistent Disk SSD
- Scalability: 10 user slots per pod, dynamic assignment
- Implementation: 6 phases (30-38 hours), daily backups with 7-day retention
- Deployment YAMLs: Current (β WORKING) vs Hybrid (π§ TESTING)
Session Exports:
- Build #17 Session 1 - Build #17 deployment readiness
- Build #17 Session 2 - Architecture evolution documentation
π Quick Startβ
# Clone the repository
git clone https://github.com/coditect-ai/Coditect-v5-multiple-llm-IDE.git
cd Coditect-v5-multiple-llm-IDE
# Install dependencies
npm install
# Start both services
./scripts/start-coditect.sh
Access the IDE:
- V5 Frontend: http://localhost:5173 (β Main application)
- IDE Backend: http://localhost:3000 (Direct IDE access)
Detailed Guide: See quickstart.md for complete instructions.
π§ͺ Testing & Quality Assuranceβ
Comprehensive testing infrastructure with automated CI/CD
# Run all tests locally
./scripts/test-runner.sh
# Frontend tests with watch mode
npm run test:watch
# Backend tests
cd backend && cargo test
# Coverage reports
npm run test:coverage
Testing Documentation:
- π Testing Strategy - Complete methodology and framework documentation
- π Implementation Guide - Detailed setup and usage instructions
- π Branch Protection Setup - Quality gates and repository protection
- βοΈ CI/CD Pipeline - Automated testing workflow
Quality Metrics:
- β 70%+ Test Coverage across frontend and backend
- β Automated Security Scanning for dependencies
- β Type Safety Enforcement with TypeScript
- β Code Quality Gates on all pull requests
π Project Statusβ
Current Phase: β BUILD #18 OPERATIONAL - Pods Healthy, Ready for MVP Scaling
Latest Updates (2025-10-28)β
β Build #18 Deployed Successfully
- Fixed CrashLoopBackOff (permission denied errors)
- Non-root execution working (coditect user UID 1001)
- All pods healthy and serving traffic on GKE
- Image:
8449bd02-7a28-4de2-8e26-7618396b3c2f
β οΈ MVP Scaling Requirement
- Current: 3 pods (3-6 user capacity)
- Required: 10-15 pods for 20 user MVP launch
- Cost: $150/month β $500-750/month
- Action needed: Scale + deploy HPA before beta testing
- Production V5 frontend build ready (dist/ folder, 1.2 MB)
β Session Documentation Created
- Docker Build Session - Complete V5+theia architecture deep dive, build strategy, testing procedures, troubleshooting guide with ~27 minute build timeline
- Quick Reference Card - Fast command reference for Docker build, testing, and deployment
- Checkpoint Status - Current deployment status and next steps
β Combined Deployment Architecture
- Single-container deployment strategy (V5 + theia + NGINX)
- 9 deployment files created (Dockerfiles, NGINX config, Cloud Build, K8s manifests)
- Complete documentation: Architecture diagrams, deployment guides, troubleshooting
Previous Updates (2025-10-08)β
β Coditect AI Branding Implementation
- Custom "Coditect AI Agents" welcome message in theia AI Chat
- Custom robot logo (SVG)
- Agent instructions: @Coditect-Code-Generator, @Coditect-UI-Designer, @Coditect-Code-Reviewer
- Fixed InversifyJS "Ambiguous match" error using
rebind()pattern
β V5 Frontend Wrapper
- React 18 + Vite 5 dev server running on port 5173
- Apple-quality design system with 500+ design tokens
- 28 complete pages (Login, Settings, Documentation, etc.)
- Mobile-first design with 56px touch targets
- Embeds theia IDE in workspace tab
β Startup Scripts
scripts/start-coditect.sh- Start both services (foreground/background)scripts/stop-coditect.sh- Stop all services cleanly- Comprehensive logging and status reporting
π€ Claude Code Configuration (READ FIRST!)β
π .claude/ Directory - Essential Claude Code setup and agent resources:
.claude/CLAUDE.md- Autonomous Development Mode, Context Engineering, Project Configuration.claude/README.md- Directory structure and quick start guide
π Available Agents & Commands (Updated: 2025-10-14):
3. .claude/agents/ - 6 custom agents (codebase-analyzer, codebase-locator, pattern-finder, thoughts-analyzer, web-search-researcher)
4. .claude/commands/ - 24 workflow commands (create_plan, implement_plan, research_codebase, debug, ci_commit, create_handoff, etc.)
5. .claude/agents-reference/ - 84 community agents (backend-architect, rust-pro, typescript-pro, database-architect, security-auditor, cloud-architect) - Git submodule
6. .claude/commands-reference/ - 42 development tools (security-scan, api-scaffold, db-migrate, monitoring-setup) - Git submodule
π Reference Materials (Updated: 2025-10-14):
7. archive/coditect-v4/ - V4 Reference (19 FDB data models, 88 ADRs, agent patterns) - Git submodule
archive/coditect-v4/docs/reference/database-models/- Complete V4 data model documentation
archive/agents-research-plan-code/- Agent Research (Multi-llm patterns, human-in-loop) - Git submoduledocs/analysis-human-layer/- 10 analysis documents (architecture, tech stack, llm integration strategies)
Why read .claude/ first?
- π Autonomous Mode: Enables multi-hour coding sessions with state tracking (DELIBERATION, RESEARCH, ACTION modes)
- π― Context Engineering: Anthropic best practices for efficient token usage and long-horizon tasks
- π€ Specialized Agents: Production-ready agents for Rust, TypeScript, FoundationDB, GCP, and more
- π οΈ Development Tools: Security scanning, API generation, database migrations, monitoring setup
- π Community Knowledge: 15 multi-agent workflows and extensive examples
- π V4 Patterns: Complete reference for FDB data models and agent architectures
- π¬ Research: Multi-llm integration analysis and human-in-the-loop patterns
π― Overviewβ
Coditect AI IDE is a next-generation browser-based integrated development environment that combines:
- π§ 16+ Local llm Models via LM Studio (no cloud required)
- π€ Multi-Agent System with MCP and A2A protocols
- π Multi-Session workspaces for parallel project work
- π» VS Code-Like Experience built on Eclipse theia 1.65
- π Privacy-First with local-only processing
- π Browser-Based with no installation needed
Two-Service Architectureβ
βββββββββββββββββββββββββββββββββββββββ
β V5 Frontend Wrapper (React + Vite) β Port 5173
β ββ Header & Navigation β
β ββ 28 Complete Pages β
β ββ Settings (8 sections) β
β ββ workspace Tab (embeds theia) β
βββββββββββββββββββ¬ββββββββββββββββββββ
β
βΌ
βββββββββββββββββββββββββββββββββββββββ
β theia Backend (Eclipse theia) β Port 3000
β ββ Monaco editor β
β ββ File Explorer β
β ββ terminal (xterm.js) β
β ββ AI Chat (Coditect Branding) β
βββββββββββββββββββββββββββββββββββββββ
π¨ Key Featuresβ
theia Backend (Port 3000)β
- β Eclipse theia 1.65 - Complete IDE framework
- β Custom Branding - "Coditect AI Agents" with robot logo
- β Monaco editor - Full VS Code editing experience
- β AI Chat - Integrated AI assistance with custom agents
- β File Explorer - Complete file tree navigation
- β terminal - Integrated xterm.js terminal
- β Extensions - VS Code extension compatible
V5 Frontend Wrapper (Port 5173)β
- β Apple-Quality Design System - 500+ design tokens, unified theme
- β Mobile-First - Touch-friendly with 56px tap targets
- β
28 Complete Pages - Full application flow
- Login, Register, Profile
- Settings (8 sections with TouchFriendlyCard)
- Documentation Hub (18 sub-pages)
- AI Studio Tab (Loveable-style interface)
- workspace Tab (theia iframe)
- FAQ, Support, Status
- β React 18 + TypeScript - Modern React with full type safety
- β Vite 5 - Lightning-fast HMR and dev server
- β Chakra UI 2.8 - Accessible component library
Multi-llm Supportβ
- π§ LM Studio - 16+ local models (Qwen, Llama, DeepSeek, etc.)
- π€ Claude Code - Anthropic's coding assistant
- π¦ Ollama - Easy local llm deployment
- π OpenAI - Optional cloud API
- π Gemini - Google's multimodal AI
- β‘ Grok - xAI's conversational AI
Agent Systemβ
Hierarchical Agents:
Coordinator Agent
βββ Code Generation Agent (@Coditect-Code-Generator)
β βββ TypeScript Sub-Agent
β βββ Python Sub-Agent
β βββ Rust Sub-Agent
βββ UI Design Agent (@Coditect-UI-Designer)
β βββ React Sub-Agent
β βββ CSS Sub-Agent
βββ Code Review Agent (@Coditect-Code-Reviewer)
βββ Security Review
βββ Performance Review
βββ Style Review
Protocols:
- MCP (Model Context Protocol) - Tool/resource access
- A2A (Agent-to-Agent) - Agent collaboration
π Deployment Statusβ
Production Deployment (GCP)β
Infrastructure: serene-voltage-464305-n2
- β
GKE Cluster:
codi-poc-e2-cluster(us-central1-a) - β
FoundationDB: 3-node StatefulSet at
10.128.0.8:4500 - β
Domain/SSL:
coditect.aiwith Google-managed certificate - β
Container Registry:
gcr.io/serene-voltage-464305-n2
Deployment Architecture:
βββββββββββββββββββββββββββββββββββββββ
β Docker Container (Port 80) β
βββββββββββββββββββββββββββββββββββββββ€
β NGINX β
β βββ / β V5 Frontend (dist/) β
β βββ /theia β theia (localhost:3000)β
β β
β Node.js (Port 3000) β
β βββ Eclipse theia IDE β
βββββββββββββββββββββββββββββββββββββββ
Deployment Files:
- deployment/dockerfile.local-test - Production build (uses pre-built dist/)
- deployment/nginx-combined.conf - NGINX routing configuration
- start-combined.sh - Container startup script
- deployment/cloudbuild-combined.yaml - Google Cloud Build config
- deployment/k8s/k8s-combined-deployment.yaml - Kubernetes manifests
- DEPLOYMENT-architecture.md - Complete architecture docs
- deployment-summary.md - Quick reference guide
- deploy-combined.md - Step-by-step deployment
- checkpoint-docker-setup.md - Current status & next steps
Next Steps:
- Install Docker client for local testing
- Test build:
docker build -f deployment/dockerfile.local-test -t coditect-combined:test . - Deploy to Cloud Build:
gcloud builds submit --config deployment/cloudbuild-combined.yaml - Deploy to GKE cluster
π§ͺ Deployment & Testing Infrastructureβ
Created: 2025-10-14 Status: β Complete and Operational
Overviewβ
Automated testing suite that catches ALL 9 deployment issues in < 2 minutes, BEFORE wasting 10-20 minutes on Cloud Build.
Impact:
- β‘ 79% faster (80-160 min β 17 min per deployment)
- π° $40-80 saved per incident (no failed builds)
- β Zero failed deployments from config issues
- π¨ Catches issues early (< 2 min local test vs 10-20 min Cloud Build)
Testing Infrastructureβ
- testing-infrastructure-complete.md - Complete automated testing suite overview
- docs/testing-summary.md - Quick reference guide
- docs/testing-guide.md - Complete documentation (558 lines)
Test Scriptsβ
Pre-Deployment Validation:
- scripts/test-deployment.sh - Comprehensive validation (403 lines)
- Tests 9 categories: config, source code, build, Docker, NGINX, Cloud Build, K8s
- Runs in < 2 minutes
- Exit code 0 = safe to deploy, 1 = issues found
Live Endpoint Testing:
- scripts/test-endpoints.sh - Production endpoint verification (122 lines)
- Tests health, frontend, API paths, old path 404s
- Runs in < 10 seconds
- Usage:
./scripts/test-endpoints.sh https://coditect.ai
Convenient Commands:
- Makefile - Easy-to-remember test commands (73 lines)
make test # Run all pre-deployment tests
make test-config # Quick config check (< 5 sec)
make test-build # Test build process
make test-endpoints # Test live endpoints
make deploy # Deploy (runs tests first!)
make clean # Clean build artifacts
Deployment Filesβ
Cloud Build & CI/CD:
- deployment/cloudbuild-combined.yaml - GCP Cloud Build with automated validation
- Step 0: Pre-build validation (< 1 min) - catches config issues early
- Step 1: Build + verification (~ 4 min) - validates built files
Docker & Container:
- deployment/dockerfile.local-test - Production Docker image
- deployment/dockerfile.combined - Multi-stage build
- deployment/nginx-combined.conf - NGINX routing configuration
- start-combined.sh - Container startup script
Kubernetes:
- deployment/k8s/k8s-combined-deployment.yaml - Kubernetes deployment manifests
Critical Configuration Filesβ
β οΈ MUST be correct for successful deployment:
-
.env.production - Environment variables
- CRITICAL: Must have
VITE_API_URL=/api/v5(NOT/api) - Gets compiled into JavaScript at build time by Vite
- CRITICAL: Must have
-
package.json - Build scripts
- CRITICAL: Must have
prototype:buildscript for V5 frontend "prototype:build": "tsc && vite build"β- NOT
"build": "npm run theia:build"β
- CRITICAL: Must have
Issue Trackingβ
docs/10-execution-plans/api-integration-fixes-complete.md - Complete documentation of all 9 deployment issues and fixes:
Issues #1-5 (Infrastructure):
- β Frontend auth check missing
- β
Duplicate
/v5API paths - β NGINX proxy route missing
- β Incomplete Kubernetes DNS name
- β GCP Ingress routing to wrong backend
Issues #6-9 (Build & Config): 6. β Docker layer caching (reused stale dist/) 7. β npm package-lock.json sync issues 8. β Wrong build script (theia:build vs prototype:build) 9. β Wrong environment variable (VITE_API_URL=/api vs /api/v5)
Quick Testing Workflowβ
# Before every deployment
make test-config # < 5 seconds - config check
make test # ~ 2 minutes - full validation
# If tests pass, deploy
make deploy # Automatic Cloud Build
# After deployment, verify
make test-endpoints # ~ 10 seconds - live verification
Test Demonstrationβ
Catches Wrong Configuration:
# Simulate wrong config
sed -i 's|/api/v5|/api|' .env.production
# Run test
make test-config
# Output: β .env.production is wrong!
# Result: β
Test correctly prevents bad deployment
π§ Socket.IO Investigation & Troubleshootingβ
Created: 2025-10-20 Status: β³ In Progress - Multiple root causes identified, fixes being applied
Problem Statementβ
Users accessing theia IDE at https://coditect.ai/theia experience HTTP 400 Bad Request errors when establishing Socket.IO connections. This breaks real-time features including:
- terminal sessions
- File watching
- Live code collaboration
- Auto-save functionality
Investigation Findingsβ
TWO Root Causes Identified:
-
β CDN Caching (FIXED) - GCP Cloud CDN was caching Socket.IO requests with stale session IDs
- Solution: Disabled CDN in BackendConfig (
k8s/backend-config-no-cdn.yaml) - Validation: CDN headers removed from responses
- Solution: Disabled CDN in BackendConfig (
-
β³ Session Affinity Missing (IN PROGRESS) - GCP backend service shows
SESSION_AFFINITY: NONE- Problem: Service missing BackendConfig annotation (NEG requirement)
- Solution: Annotated Service with BackendConfig reference
- Status: Propagating to GCP load balancer (2-5 minutes)
Additional Fixes Recommended (from reference docs):
- P0: WebSocket annotation to Ingress (85% success probability)
- P0: Health check endpoint creation (70% success probability)
- P1: Increased backend timeout and connection draining optimization
Comprehensive Documentationβ
Investigation Package (~150 pages of analysis):
-
socket.io-issue/analysis-troubleshooting-guide.md - START HERE (20KB)
- Complete investigation findings and evidence chain
- Diagnostic commands for each system layer
- Fix procedures with validation tests
- Integration with reference documentation
- Success criteria and monitoring recommendations
-
socket.io-issue/additional-research-pathways.md (19KB)
- High-value research pathways (P0-P2)
- Quick wins and emergency rollback procedures
- Long-term improvements (monitoring, health checks, regression tests)
- Learning opportunities for team
-
socket.io-issue/README.md - Investigation package index
- 8 comprehensive documents (~150 pages)
- Quick navigation by role (Executive, Engineer, On-Call)
- Quick start guide for immediate issue resolution
- Implementation checklist
-
Reference Documentation (from investigation package):
- executive-summary.md - High-level overview with 5 prioritized fixes
- quick-reference.md - Emergency cheat sheet (2 minutes)
- investigation-runbook.md - Step-by-step diagnostic procedures (20 pages)
- diagnostic-decision-tree.md - Structured troubleshooting logic (15 questions)
- fix-implementation-guide.md - Detailed fix procedures with validation tests (30 pages)
- architecture-diagrams.md - Visual representation of system and issues (8 Mermaid diagrams)
- socketio-diagnostics.sh - Automated diagnostic script (400 lines bash)
Quick Testing Workflowβ
# Test Socket.IO inside cluster
kubectl exec -n coditect-app deployment/coditect-combined -- \
curl -s -o /dev/null -w "%{http_code}\n" \
http://localhost/theia/socket.io/?EIO=4\&transport=polling
# Test via Ingress
curl -s -o /dev/null -w "%{http_code}\n" \
https://coditect.ai/theia/socket.io/?EIO=4\&transport=polling
# Run automated diagnostics
chmod +x socket.io-issue/socketio-diagnostics.sh
./socket.io-issue/socketio-diagnostics.sh --verbose
Next Stepsβ
- β Validate session affinity propagation (check GCP backend service)
- π Apply WebSocket annotation to Ingress
- π Create
/healthendpoint in nginx - π Run automated diagnostic script for comprehensive validation
- π Test at https://coditect.ai/theia after all fixes applied
- π Monitor Socket.IO connection success rates for 24 hours
- π Implement long-term improvements (monitoring dashboard, automated health checks)
Related Filesβ
Configuration:
k8s/backend-config-no-cdn.yaml- BackendConfig with CDN disablednginx-combined.conf- NGINX routing with WebSocket supportdocs/fixes/socket-io-cdn-fix.md- Initial CDN fix documentation
See Also:
- CLAUDE.md - Complete status and investigation timeline
- Testing Infrastructure - Pre-deployment validation (below)
π Deployment Archeology - Finding Previous Successful Buildsβ
When deployment fails, use deployment archeology to find what worked before.
Quick Processβ
# 1. Get deployment creation date
kubectl get deployment <NAME> -n coditect-app -o jsonpath='{.metadata.creationTimestamp}'
# 2. Find successful builds on that date
gcloud builds list --filter="createTime>='YYYY-MM-DDT00:00:00Z'" --limit=20
# 3. Analyze successful build config
gcloud builds describe <BUILD_ID> --format="yaml(steps,options)"
# 4. Search git history for files
git log --all --full-history -- <FILENAME>
# 5. Restore archived files if needed
cp docs/99-archive/deployment-obsolete/<FILE> ./<FILE>
Real Example: Combined Service Recovery (Oct 18, 2025)β
Problem: dockerfile.combined failing to build (npm ci errors, Python missing, wrong build script)
Solution Found:
- Deployment created: 2025-10-13T09:58:29Z
- Successful build: 6e95a4d9 at 09:50:07Z (8 min before deployment)
- Used file: dockerfile.local-test (archived, not dockerfile.combined!)
- Machine: E2_HIGHCPU_32 (32 CPUs, NOT 8 CPUs)
- Node memory: 8GB heap (
NODE_OPTIONS=--max_old_space_size=8192) - Pre-requisite: Build frontend first (
npm run buildcreates dist/)
Key Configuration:
# cloudbuild-combined.yaml
steps:
- name: 'gcr.io/cloud-builders/docker'
args: ['-f', 'dockerfile.local-test', ...] # NOT dockerfile.combined
options:
machineType: 'E2_HIGHCPU_32' # 32 CPUs for theia webpack
env:
- 'NODE_OPTIONS=--max_old_space_size=8192' # 8GB heap
Recovery Steps:
# Restore working Dockerfile
cp docs/99-archive/deployment-obsolete/dockerfile.local-test ./
# Update cloudbuild-combined.yaml
# - Change: dockerfile.combined β dockerfile.local-test
# - Change: N1_HIGHCPU_8 β E2_HIGHCPU_32
# - Add: NODE_OPTIONS=--max_old_space_size=8192
# Build frontend first (CRITICAL!)
npm run build # Creates dist/ folder
# Deploy with proven config
gcloud builds submit --config cloudbuild-combined.yaml .
Automation Scriptβ
Location: .claude/skills/deployment-archeology/SKILL.md
#!/bin/bash
# deployment-archeology.sh - Find previous successful build config
DEPLOYMENT=$1
NAMESPACE=${2:-default}
echo "=== Deployment Archeology ==="
# Step 1: Get deployment date
DEPLOY_DATE=$(kubectl get deployment $DEPLOYMENT -n $NAMESPACE -o jsonpath='{.metadata.creationTimestamp}')
SEARCH_DATE=$(date -d $DEPLOY_DATE '+%Y-%m-%d')
echo "Deployment created: $DEPLOY_DATE"
echo "Searching builds on: $SEARCH_DATE"
# Step 2: Find builds on that date
gcloud builds list \
--filter="createTime>='${SEARCH_DATE}T00:00:00Z' AND createTime<='${SEARCH_DATE}T23:59:59Z'" \
--format="table(id,status,createTime)" \
--limit=20
# Step 3: Show git commits around that date
git log --since="$SEARCH_DATE" --until="$(date -d "$SEARCH_DATE + 1 day" '+%Y-%m-%d')" --oneline --all | head -20
echo ""
echo "Next steps:"
echo "1. Identify successful build ID (STATUS=SUCCESS)"
echo "2. Run: gcloud builds describe <BUILD_ID> --format='yaml(steps,options)'"
echo "3. Check for archived files: find . -name 'Dockerfile*' | grep archive"
echo "4. Compare current config vs successful build config"
Common Gotchasβ
- β Assuming current files match deployed version
- β Not checking environment variables in Cloud Build options
- β Forgetting to check for archived/moved files
- β Using wrong Dockerfile (may have multiple variants)
- β Missing build prerequisites (like pre-built
dist/directory)
See Alsoβ
- Skill Documentation:
.claude/skills/deployment-archeology/SKILL.md - CLAUDE.md: Deployment archeology section with detailed examples
- Testing Guide:
docs/testing-guide.mdfor pre-deployment validation
π Project Structureβ
/workspace/PROJECTS/t2/
βββ quickstart.md # β Quick start guide
βββ README.md # This file
βββ CLAUDE.md # Claude Code instructions
βββ checkpoint-docker-setup.md # β Current deployment status
βββ start-coditect.sh # Start both services
βββ stop-coditect.sh # Stop all services
β
βββ dockerfile.local-test # π Production Docker build
βββ dockerfile.combined # Alternative build (has Python issue)
βββ nginx-combined.conf # NGINX routing config
βββ start-combined.sh # Container startup script
βββ cloudbuild-combined.yaml # Google Cloud Build config
βββ k8s-combined-deployment.yaml # Kubernetes manifests
βββ DEPLOYMENT-architecture.md # Architecture documentation
βββ deployment-summary.md # Quick reference
βββ deploy-combined.md # Deployment guide
β
βββ .claude/ # π€ CLAUDE CODE CONFIGURATION (READ THIS!)
β βββ CLAUDE.md # Autonomous mode, context engineering, project config
β βββ README.md # Directory structure and quick start
β βββ CLAUDE-GLOBAL-REFERENCE.md # Reference from global .claude repo
β βββ settings.local.json # Auto-approved commands, MCP servers
β βββ agents/ # 8 custom project-specific agents
β β βββ orchestrator.md # π― Multi-agent orchestrator (production workflows)
β β βββ codebase-analyzer.md
β β βββ codebase-locator.md
β β βββ codebase-pattern-finder.md
β β βββ project-organizer.md
β β βββ thoughts-analyzer.md
β β βββ thoughts-locator.md
β β βββ web-search-researcher.md
β βββ skills/ # β‘ 15 AUTOMATION SKILLS (CHECK FIRST!)
β β βββ REGISTRY.json # π Fast skill lookup index
β β βββ README.md # Skill discovery documentation
β β βββ build-deploy-workflow/ # Build + Deploy + Document (saves 40 min)
β β βββ gcp-resource-cleanup/ # Clean legacy GCP (saves 28 min, $50-100/mo)
β β βββ git-workflow-automation/ # Git operations (saves 8 min)
β β βββ cross-file-documentation-update/ # Sync 4 docs (saves 13 min)
β β βββ deployment-archeology/ # Find previous successful deployments
β β βββ foundationdb-queries/ # FDB patterns + tenant isolation
β β βββ rust-backend-patterns/ # Actix-web patterns
β β βββ search-strategies/ # Grep/Glob optimization
β β βββ framework-patterns/ # Event-driven, FSM patterns
β β βββ evaluation-framework/ # llm-as-judge patterns
β β βββ production-patterns/ # Circuit breakers, error handling
β β βββ communication-protocols/ # Multi-agent handoff
β β βββ google-cloud-build/ # Cloud Build optimization
β β βββ internal-comms/ # Team communication
β β βββ multi-agent-workflow/ # Token management, orchestration
β βββ scripts/ # π οΈ Automation scripts
β β βββ build-skill-registry.py # Generate REGISTRY.json
β βββ commands/ # 52 workflow commands (24 custom + 28 reference)
β β βββ create_plan.md, implement_plan.md, research_codebase.md
β β βββ ci_commit.md, debug.md, local_review.md
β β βββ create_handoff.md, resume_handoff.md
β β βββ ... (52 total commands)
β βββ hooks/ # Pre/post execution hooks
β β βββ README.md
β βββ agents-reference/ # Git submodule: 84 specialized agents
β β βββ agents/ # backend-architect, rust-pro, typescript-pro, etc.
β β βββ workflows/ # Multi-agent orchestration (15 workflows)
β β βββ tools/ # Development utilities
β βββ commands-reference/ # Git submodule: 42 development tools
β βββ tools/ # security-scan, api-scaffold, db-migrate, etc.
β βββ workflows/ # Command coordination patterns
β βββ examples/ # Usage examples
β
βββ theia-app/ # theia Backend (Port 3000)
β βββ coditect-branding-solution.md # Branding implementation guide
β βββ src/browser/
β β βββ coditect-branding-frontend-module.ts # Custom branding
β β βββ coditect-chat-welcome-provider.tsx # Custom AI Chat
β βββ src-gen/frontend/ # Generated theia code
β βββ lib/ # Compiled JavaScript
β βββ package.json # theia dependencies
β
βββ src/ # V5 Frontend Source (Port 5173)
β βββ components/ # React components
β β βββ theia/ # theia widget wrappers
β β βββ ai-studio/ # AI Studio Tab
β β βββ workspace/ # workspace Tab
β βββ pages/ # 28 complete pages
β βββ theme/ # Apple-quality design system
β βββ services/ # API integration
β βββ stores/ # Zustand state management
β βββ agents/ # Custom agent definitions
β βββ app.tsx # Main app with 28 routes
β βββ main.tsx # Entry point
β
βββ docs/ # Documentation
β βββ DEFINITIVE-V5-architecture.md # β Complete V5 design
β βββ apple-quality-design-system.md # Design principles
β βββ v5-frontend-build-verification.md # Build status
β βββ theia-ai-research-findings.md # theia 1.65 capabilities
β βββ 01-getting-started/ # Quick start guides
β βββ 02-architecture/ # SDD, TDD, architecture
β βββ 03-infrastructure/ # GCP, FoundationDB
β βββ 04-security/ # Security hardening
β βββ 07-adr/ # Architecture decisions
β βββ 08-v4-reference/ # V4 reference materials
β βββ 10-execution-plans/ # Deployment tracking
β βββ 11-analysis/ # System analysis & provisioning strategies
β β βββ monitor-codi-container-provisioning-strategy.md # π File monitoring & agent coordination (HYBRID approach)
β βββ analysis-human-layer/ # π Multi-llm integration analysis (NEW)
β βββ 01-executive-summary.md
β βββ 02-architectural-deep-dive.md
β βββ 08-multi-llm-technical-implementation-details.md
β βββ llm-implementations/ # Claude, Gemini, Grok, OpenAI patterns
β
βββ archive/ # π¦ Reference Materials & Research (NEW)
β βββ coditect-v4/ # Git submodule: V4 reference
β β βββ docs/reference/database-models/ # 19 FDB data models
β β βββ docs/07-adr/ # 88 ADRs from V4
β β βββ agents/ # V4 agent system patterns
β βββ agents-research-plan-code/ # Git submodule: Agent research
β βββ .claude/ # Agent and command templates
β βββ docs/ # Research documentation
β
βββ backend/ # Rust Backend (GCP Deployment)
β βββ src/ # Actix-web API
β βββ Dockerfile # Production Docker image
β βββ cloudbuild.yaml # GCP Cloud Build config
β
βββ scripts/ # Utility scripts
β βββ fix-doc-links.sh # Fix documentation links
β
βββ .backup/ # Backup files
βββ package.json # Root dependencies
βββ vite.config.ts # Vite configuration
βββ tsconfig.json # TypeScript configuration
π Getting Startedβ
Prerequisitesβ
- Node.js 20+ (LTS recommended)
- npm or yarn
- LM Studio (optional, for local llm support)
- Git for version control
Installationβ
# 1. Clone repository
git clone https://github.com/coditect-ai/Coditect-v5-multiple-llm-IDE.git
cd Coditect-v5-multiple-llm-IDE
# 2. Install dependencies
npm install
# 3. Install theia dependencies
cd theia-app
npm install
cd ..
Running the Applicationβ
Option 1: Use Convenience Scripts (Recommended)β
# Start both services in background
./scripts/start-coditect.sh
# OR start in foreground (Ctrl+C stops both)
./scripts/start-coditect.sh --foreground
# Stop all services
./scripts/stop-coditect.sh
Option 2: Manual Startβ
# terminal 1: Start theia backend
cd theia-app
npm start
# Runs on http://localhost:3000
# terminal 2: Start V5 frontend wrapper
cd ..
npm run prototype:dev
# Runs on http://localhost:5173
Accessing the IDEβ
-
β V5 Frontend (Main): http://localhost:5173
- Complete Coditect UI with all pages
- workspace tab embeds theia IDE
-
theia Direct: http://localhost:3000
- Direct access to Eclipse theia
- AI Chat with Coditect branding
- Useful for testing theia features
π οΈ Developmentβ
Build Commandsβ
# V5 Frontend (Vite has HMR - auto-reload on changes)
npm run prototype:dev # Start dev server
npm run prototype:build # Production build
npm run prototype:preview # Preview production build
# theia Backend (requires manual rebuild)
cd theia-app
npm run theia:build # Build theia
npm run theia:watch # Watch mode
npm run theia:start # Start server
Rebuilding theia After Changesβ
If you modify theia source files (branding, extensions):
cd theia-app/src/browser
npx tsc # Compile TypeScript
cd ../..
npx webpack --config gen-webpack.config.js # Rebuild bundle
npm start # Restart theia
Type Checkingβ
# V5 Frontend
npm run type-check
# theia
cd theia-app && npm run type-check
π³ Development Modesβ
Coditect AI IDE supports multiple deployment modes for different development scenarios:
| Mode | Best For | terminal | Git Integration |
|---|---|---|---|
| Container-Only | Production, Cloud (GKE) | Container OS (Debian) | Manual setup required |
| Volume Mount | Local development | Container + Host files | Host config (automatic) |
| Remote SSH (Future) | Remote dev servers | Remote machine | Native on remote |
| Native Desktop | Single-user local | Host OS native | Native |
Quick Start by Modeβ
Production Mode (Container-Only)β
# Build Docker image
docker build -f deployment/dockerfile.local-test -t coditect-combined:prod .
# Run container
docker run -d -p 8080:80 --name coditect-prod coditect-combined:prod
# Access:
# - V5 Frontend: http://localhost:8080/
# - theia IDE: http://localhost:8080/theia/
Git Setup:
# Enter container
docker exec -it coditect-prod bash
# Configure git
git config --global user.name "Your Name"
git config --global user.email "you@example.com"
Local Development Mode (Volume Mount)β
Windows (PowerShell):
docker run -d `
-p 8080:80 `
-v C:\Users\YourUser\Projects:/workspace `
-v C:\Users\YourUser\.gitconfig:/root/.gitconfig:ro `
-v C:\Users\YourUser\.ssh:/root/.ssh:ro `
--name coditect-dev `
coditect-combined:test
Mac/Linux (Bash):
docker run -d \
-p 8080:80 \
-v ~/projects:/workspace \
-v ~/.gitconfig:/root/.gitconfig:ro \
-v ~/.ssh:/root/.ssh:ro \
--name coditect-dev \
coditect-combined:test
Benefits:
- β Edit files on your machine
- β Git works automatically (uses host config)
- β Files persist after container restart
- β Fast development iteration
terminal & workspace Connectivityβ
Where does the theia terminal connect?
-
Container-Only: terminal runs inside Docker container (Debian Linux)
- Isolated from host system
- Complete security isolation
- Best for production/multi-tenant
-
Volume Mount: terminal runs in container but accesses host files
- Edit local files while using container runtime
- Git automatically uses host SSH keys
- Best for local development
-
Remote SSH (Future): terminal connects to remote machine via SSH
- Access powerful remote dev servers
- Run commands on production-like environments
- Requires theia SSH extension
-
Native Desktop: terminal runs on host OS (Windows/Mac/Linux)
- Direct OS integration
- Best for single-user local installs
Documentationβ
For detailed configuration, troubleshooting, and platform-specific instructions:
- π User Guide:
docs/01-getting-started/development-modes.md - π§ Technical Reference:
docs/01-getting-started/docker-volume-configuration.md - π Architecture Decision:
docs/07-adr/adr-025-terminal-workspace-connectivity-options.md - π theia Integration:
docs/V5-THEIA-WRAPPER-architecture.md
π Documentationβ
Essential Readingβ
- quickstart.md - Get started in 5 minutes
- CLAUDE.md - Instructions for Claude Code
- docs/DEFINITIVE-V5-architecture.md - Complete V5 design
- docs/apple-quality-design-system.md - Design principles
- theia-app/coditect-branding-solution.md - Branding implementation
Documentation Indexβ
- Architecture:
docs/02-architecture/- SDD, TDD, system design - Infrastructure:
docs/03-infrastructure/- GCP, FoundationDB, deployment - Security:
docs/04-security/- Security hardening plans - ADRs:
docs/07-adr/- Architecture Decision Records (ADR-001 to ADR-024) - V4 Reference:
docs/08-v4-reference/- V4 patterns (reference only) - Execution Plans:
docs/10-execution-plans/- Deployment tracking
Full documentation index: docs/DOCUMENTATION-index.md
ποΈ Architectureβ
Technology Stackβ
| Layer | Technology | Version | Purpose |
|---|---|---|---|
| Frontend | React | 18.3 | UI framework |
| TypeScript | 5.3 | Type safety | |
| Vite | 5.4 | Dev server & build | |
| Chakra UI | 2.8 | Component library | |
| IDE | Eclipse theia | 1.65 | IDE framework |
| Monaco editor | 0.45 | Code editor | |
| xterm.js | 5.3 | terminal | |
| Backend | Rust (Actix-web) | Latest | API server |
| FoundationDB | 7.1+ | Database | |
| llm | LM Studio | Latest | Local llm inference |
| Claude Code | Latest | AI assistance | |
| State | Zustand | 4.4 | State management |
Infrastructure (GCP)β
Project: serene-voltage-464305-n2
| Component | Status | Details |
|---|---|---|
| GKE Cluster | β Live | codi-poc-e2-cluster (us-central1-a) |
| FoundationDB | β Live | 3-node StatefulSet at 10.128.0.8:4500 |
| Domain/SSL | β Active | coditect.ai (Google-managed cert) |
| Container Registry | β Ready | gcr.io/serene-voltage-464305-n2 |
| CI/CD | β Ready | Cloud Build pipelines |
π€ llm Workflowsβ
Supported Modesβ
- Single Mode - One llm at a time
- Parallel Mode - Side-by-side comparison
- Sequential Mode - Chained processing (LM Studio β Claude)
- Consensus Mode - Synthesized best answer from multiple llms
Recommended Models (LM Studio)β
For AMD Ryzen AI Max+ 395 (128GB RAM):
| Model | Size | RAM | Best For |
|---|---|---|---|
| Meta Llama 3.3 70B | Q4_K_M | ~40GB | General coding, reasoning |
| Qwen2.5 72B | Q4_K_M | ~40GB | Multilingual, math |
| DeepSeek-Coder-V2 | Q4_K_M | ~40GB | Code generation |
| Mixtral 8x22B | Q4_K_M | ~35GB | Fast inference, MoE |
π Securityβ
- JWT Authentication - Secure session management
- RBAC - Role-based access control
- Audit Logging - Comprehensive event tracking
- Local-First - No data leaves your machine (except optional cloud providers)
- GDPR/SOC2 Ready - Compliance-ready architecture
π Current Statusβ
Completed Features β β
Development (Local):
- β Coditect AI branding in theia AI Chat
- β Custom robot logo and agent instructions
- β V5 Frontend wrapper with 28 pages
- β Apple-quality design system (500+ tokens)
- β Mobile-first design (56px touch targets)
- β Startup/shutdown scripts
- β Two-service architecture working (ports 5173 + 3000)
Deployment (GCP):
- β V5 Frontend production build (dist/ folder ready)
- β Combined deployment architecture designed
- β 9 deployment files created (Dockerfiles, configs, manifests)
- β Complete documentation (architecture, guides, troubleshooting)
- β
GKE infrastructure ready (
codi-poc-e2-cluster) - β FoundationDB ready (3-node StatefulSet)
- β
Domain/SSL configured (
coditect.ai)
In Progress πβ
- βΈοΈ Docker Installation: Need Docker client for local testing
- π Local Docker Build Test: Test dockerfile.local-test (~27 min build)
- π Cloud Build Deployment: Deploy to GCP after local test succeeds
- π GKE Deployment: Deploy to Kubernetes cluster
- π WebSocket integration: Test theia terminal in production
- π Agent system implementation: Custom agents for code generation
Roadmap π§β
- π§ Auth Backend: JWT + FoundationDB sessions (Phase 3)
- π§ WebSocket Sidecar: Real-time communication layer (Phase 4)
- π§ Pod auto-provisioning: User workspace isolation (Phase 5)
- π§ Full Integration: End-to-end testing (Phase 6)
- π§ Blue-green rollout: Zero-downtime deployment (Phase 7)
- π§ Production monitoring: Prometheus + Grafana dashboards
π€ Contributingβ
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
Development Workflowβ
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit changes (
git commit -m 'feat: Add amazing feature') - Push to branch (
git push origin feature/amazing-feature) - Open a Pull Request
π Licenseβ
This project is licensed under the Eclipse Public License 2.0 (EPL-2.0).
Eclipse theia is EPL-2.0 licensed, which allows free commercial use without licensing fees.
See LICENSE for details.
π Linksβ
- GitHub: https://github.com/coditect-ai/Coditect-v5-multiple-llm-IDE
- Website: https://coditect.ai
- Documentation: https://coditect.ai/docs
- Issues: https://github.com/coditect-ai/Coditect-v5-multiple-llm-IDE/issues
π Supportβ
- Discord: Join our community
- Email: support@coditect.ai
- Documentation: See docs/ folder
π Acknowledgmentsβ
- Eclipse theia Team - Amazing IDE framework
- Anthropic - Claude Code and MCP protocol
- LM Studio - Local llm inference
- Contributors - Everyone who helped build this
Made with β€οΈ by the Coditect AI Team
Last Updated: 2025-10-12 | Status: Deployment architecture ready, awaiting Docker installation