Architecture Overview
System Design
VibeTunnel consists of three main components working together:Component Responsibilities
macOS Application
Server Process
Web Frontend
Data Flow
Session Creation
Terminal I/O
Session Cleanup
Communication Protocols
HTTP REST API
- Session CRUD operations
- Authentication endpoints
- Health checks
- See API Reference
WebSocket Protocol
- Terminal transport:
/wsWebSocket v3 framing (multiplexed sessions) - Details:
docs/websocket.md
Inter-Process Communication
- Mac app spawns Bun server as child process
- Environment variables for configuration
- File-based PID tracking
- Signal handling for graceful shutdown
Security Architecture
Authentication Flow
Network Security
- Localhost-only by default
- Optional LAN exposure with authentication
- Tailscale/ngrok integration for remote access
- WSS/HTTPS in production
Process Isolation
- Each session runs in separate PTY process
- User permissions inherited from server
- No privilege escalation
- Resource limits per session
Performance Optimizations
Buffer Aggregation
- Batch terminal output every 16ms
- Reduce WebSocket message frequency
- Binary protocol reduces payload size
Connection Management
- WebSocket connection pooling
- Automatic reconnection with backoff
- Ping/pong for keep-alive
Resource Management
- Lazy loading of terminal sessions
- Automatic cleanup of idle sessions
- Memory-mapped session recordings
Platform Integration
macOS Features
- Menu bar application
- Sparkle auto-updates
- Code signing & notarization
- Launch at login
iOS Features
- Native Swift UI
- Background session support
- Push notifications
- Handoff support
Web Standards
- Progressive Web App capable
- Service Worker for offline
- WebAssembly for performance
- Responsive design
Build & Deployment
Build Pipeline
Configuration
- Runtime: Environment variables
- Build-time: xcconfig files
- User preferences: macOS defaults system
- Server config: JSON files
Monitoring & Debugging
Logging
- Unified logging to macOS Console
- Structured JSON logs from server
- Session-specific log filtering
- See
./scripts/vtlog.sh
Metrics
- Session count & duration
- Message throughput
- Error rates
- Resource usage