2e6d1a67dd
Implement GuruRMM Phase 1: Real-time tunnel infrastructure
...
Complete bidirectional tunnel communication between server and agents,
enabling persistent secure channels for future command execution and
file operations. Agents transition from heartbeat mode to tunnel mode
on-demand while maintaining WebSocket connection.
Server Implementation:
- Database layer (db/tunnel.rs): Session CRUD, ownership validation,
cleanup on disconnect (prevents orphaned sessions)
- API endpoints (api/tunnel.rs): POST /open, POST /close, GET /status
with JWT auth, UUID validation, proper HTTP status codes
- Protocol extension (ws/mod.rs): TunnelOpen/Close/Data messages,
agent response handlers (TunnelReady/Data/Error)
- Migration (006_tunnel_sessions.sql): tech_sessions table with
partial unique constraint, foreign keys with CASCADE, audit table
Agent Implementation:
- State machine (tunnel/mod.rs): AgentMode (Heartbeat ↔ Tunnel),
channel multiplexing, concurrent session prevention
- WebSocket handlers (transport/websocket.rs): Open/close tunnel,
mode switching without dropping connection, cleanup on disconnect
- Protocol extension (transport/mod.rs): TunnelReady/Data/Error
messages matching server definitions
- Unit tests: Lifecycle and channel management coverage
Key Features:
- Security: JWT auth, session ownership verification, SQL injection
prevention, constraint-based duplicate session blocking
- Cleanup: Automatic session closure on agent disconnect (both sides),
channel cleanup, graceful state transitions
- Error handling: Proper HTTP status codes (400/403/404/409/500),
comprehensive Result types, detailed logging
- Extensibility: Channel types ready (Terminal/File/Registry/Service),
TunnelDataPayload enum for Phase 2+ expansion
Phase 1 Scope (Implemented):
- Tunnel session lifecycle management
- Mode switching (heartbeat ↔ tunnel)
- Protocol message routing
- Database session tracking
Phase 2 Next Steps:
- Terminal command execution (tokio::process::Command)
- Client WebSocket connections for output streaming
- Command audit logging
- File transfer operations
Verification:
- Server compiles successfully (0 errors)
- Agent unit tests pass (tunnel lifecycle, channel management)
- Code review approved (protocol alignment verified)
- Database constraints enforce referential integrity
- Cleanup tested (session closure on disconnect)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2026-04-14 07:10:09 -07:00
9940faf34a
Add GuruRMM real-time tunnel architecture and planning
...
Comprehensive design for transforming agents from 30s heartbeat mode to
persistent tunnel mode, enabling Claude Code to execute commands on remote
machines through secure multiplexed WebSocket channels.
Additions:
- Complete implementation plan with 5-phase roadmap (5-7 weeks to GA)
- Detailed architecture document covering protocol, security, and MCP integration
- Database migration for tech_sessions and tunnel_audit tables
Key architectural decisions:
- Hybrid lifecycle: WebSocket persistent, tunnel is operational state
- Channel multiplexing over single WebSocket (terminal, file ops, etc.)
- Three-layer security: JWT auth, session authorization, command validation
- Custom MCP server for Claude Code integration
Next: Phase 1 implementation (tunnel open/close endpoints, agent mode state machine)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2026-04-14 06:32:16 -07:00
