)]}'
{
  "log": [
    {
      "commit": "138ec2436631f136dd2e8b4891211f896587ff00",
      "tree": "80afc394ad900e6e7a0a7b524972a303ef90ef15",
      "parents": [
        "457dfd12f281dbe9b1af8d1a7429f2977e234a6f"
      ],
      "author": {
        "name": "Sean McCullough",
        "email": "banksean@gmail.com",
        "time": "Mon Jun 02 22:42:06 2025 +0000"
      },
      "committer": {
        "name": "Sean McCullough",
        "email": "banksean@gmail.com",
        "time": "Mon Jun 02 17:52:38 2025 -0700"
      },
      "message": "loop: automatic host/container ssh port tunneling\n\nFix for #47\n\nAdd comprehensive port event monitoring and automatic SSH tunnel management\nsystem that enables real-time port forwarding for container services.\n\nContainer processes need automatic port forwarding when services start or stop\nlistening on ports during agent execution. Previously, users had to manually\ncreate SSH tunnels using commands like \u0027ssh -L8000:localhost:8888 container\u0027,\nwhich required manual intervention and knowledge of when ports become available.\n\n- Extended PortMonitor with thread-safe event storage using circular buffer\n- Added PortEvent struct with type (opened/closed), port info, and timestamps\n- Maintained backward compatibility with existing logging functionality\n- Events stored in 100-item circular buffer with efficient timestamp filtering\n\n- Added /port-events endpoint in loophttp.go for container-to-host communication\n- Supports optional \u0027since\u0027 query parameter for incremental event fetching\n- Returns JSON array of recent port events with proper error handling\n- Integrated with existing Agent interface via GetPortMonitor() method\n\n- Created TunnelManager component for host-side tunnel orchestration\n- Polls container /port-events endpoint every 10 seconds for new events\n- Automatically creates SSH tunnels when ports open using same port numbers\n- Properly cleans up tunnels when ports close or context cancels\n- Skips common system ports (SSH, HTTP, SMTP) to avoid conflicts\n\n- Integrated TunnelManager into dockerimg.LaunchContainer() workflow\n- Starts tunnel manager alongside existing container management goroutines\n- Only activates when SSH is available and configured properly\n- Uses existing SSH infrastructure and container naming conventions\n\n- Container PortMonitor detects port changes via ss -lntu command\n- Events stored with RFC3339 timestamps for precise filtering\n- Thread-safe access patterns with dedicated mutex protection\n- Circular buffer prevents unbounded memory growth\n\n- RESTful GET /port-events endpoint with time-based filtering\n- Proper JSON encoding/decoding with error handling\n- Integration with existing HTTP server infrastructure\n- Non-blocking polling pattern with configurable intervals\n\n- Uses existing SSH theater configuration and host keys\n- Creates tunnels with format: ssh -L hostPort:localhost:containerPort container\n- Background monitoring of tunnel processes with automatic cleanup\n- Proper context cancellation and resource management\n\n- Added comprehensive port event storage and filtering tests\n- HTTP endpoint testing with mock agents and proper status codes\n- Verified thread-safe access patterns and circular buffer behavior\n- All existing loop package tests continue to pass\n\n- Confirmed HTTP endpoint returns proper JSON responses\n- Validated tunnel manager integrates with container launch process\n- Verified SSH tunnel creation follows existing authentication patterns\n- Build verification confirms no regressions in existing functionality\n\n- Automatic port forwarding eliminates manual SSH tunnel management\n- Real-time port detection provides immediate service accessibility\n- Transparent integration with existing Sketch container workflow\n- Maintains all existing SSH functionality and manual override options\n\n- Clean separation between container monitoring and host tunnel management\n- Extensible event-based architecture for future port-related features\n- Minimal performance impact with efficient polling and filtering\n- Robust error handling and graceful degradation when SSH unavailable\n\nThis enhancement provides seamless port forwarding automation while maintaining\nthe reliability and security of the existing SSH infrastructure, significantly\nimproving the developer experience when working with containerized services.\n\nCo-Authored-By: sketch \u003chello@sketch.dev\u003e\nChange-ID: s6bc363ed64835e5dk\n"
    },
    {
      "commit": "364f741483c1bd2c18cb3ff2ad255c9042c5362d",
      "tree": "95ff4d67ab4707d41a0ddad1e801c55cf8bf33c7",
      "parents": [
        "6cad861fbb3dbb646d190b7a5efc2fe982ea3aa8"
      ],
      "author": {
        "name": "Sean McCullough",
        "email": "banksean@gmail.com",
        "time": "Mon Jun 02 00:55:44 2025 +0000"
      },
      "committer": {
        "name": "Sean McCullough",
        "email": "banksean@gmail.com",
        "time": "Sun Jun 01 18:29:15 2025 -0700"
      },
      "message": "loop: add periodic port monitoring to container processes\n\nPartial fix for issue #47\n\nImplement periodic port monitoring functionality that runs ss every 5 seconds\nto detect changes in container listening ports, providing visibility into port\nusage changes during sketch agent execution.\n\nProblem Analysis:\nContainer processes need visibility into port changes that occur during\nagent execution. Without monitoring, it\u0027s difficult to detect when services\nstart or stop listening on ports, which can be crucial for debugging\nand understanding application behavior.\n\nImplementation:\nAdded comprehensive port monitoring system to Agent struct:\n\n1. Port Monitoring Infrastructure:\n   - Added portMonitorMu mutex and lastPorts field to Agent struct\n   - Created startPortMonitoring() method that launches background goroutine\n   - Uses time.Ticker with 5-second intervals for periodic checks\n   - Only activates when running in container mode (IsInContainer() check)\n\n2. Port Detection Logic:\n   - updatePortState() executes ss -lntu to get listening ports\n   - Compares current port state with previous state for change detection\n   - Thread-safe port state updates using dedicated mutex\n\n3. Port Parsing and Comparison:\n   - isSSOutput() automatically detects command output format\n   - Extracts protocol and local address from port listings\n   - Returns map[string]bool for efficient port comparison\n\n4. Change Detection and Logging:\n   - logPortDifferences() identifies newly opened and closed ports\n   - Structured logging with slog for port changes\n   - Separate log entries for new ports and closed ports\n   - Non-critical operation - errors don\u0027t interrupt agent execution\n\nTechnical Details:\n- Background goroutine lifecycle tied to agent context cancellation\n- Handles IPv4/IPv6 address formats correctly\n- Only monitors LISTEN state ports, ignores other connection states\n- 5-second polling interval balances responsiveness with resource usage\n\nTesting:\n- Added comprehensive test coverage for port parsing functions\n- Verifies port difference detection logic\n- All existing loop package tests continue to pass\n- Integration test confirms no regressions in agent functionality\n\nIntegration:\n- Port monitoring starts automatically in Agent.Loop() method\n- Only enabled for container execution mode\n- Uses same context pattern as existing background tasks\n- Follows established logging and error handling patterns\n\nThis enhancement provides real-time visibility into container port\nchanges without affecting core agent functionality or performance.\n\nBenefits:\n- Real-time port change detection for debugging\n- Thread-safe implementation with proper resource cleanup\n- Comprehensive test coverage ensures reliability\n\nCo-Authored-By: sketch \u003chello@sketch.dev\u003e\nChange-ID: s9bd1b1bd0b518b2bk\n"
    }
  ]
}