Commit graph

5 commits

Author SHA1 Message Date
Hans Aschauer
14aba0a048 Implement ZMQ port management and kernel readiness checks
Container Configuration:
- Added network_mode and port_bindings to ContainerConfig
- Support for 'none', 'host', and 'bridge' network modes
- Default remains 'none' for security

Jupyter Kernel Manager:
- Dynamic port allocation for 5 ZMQ channels using socket.socket()
- _allocate_ports() finds available ports via OS binding
- Host networking mode for Jupyter kernels (network_mode='host')
- Connection file properly mounted into container
- Port bindings tracked for documentation

Kernel Readiness:
- _wait_for_kernel_ready() polls shell port until kernel responds
- Configurable timeout (30s) and poll interval (0.5s)
- Replaced time.sleep(2) with proper connectivity check
- Early return when kernel is ready

This completes the core ZMQ communication infrastructure needed
for real Jupyter kernel operation.
2026-02-07 08:16:51 +01:00
Hans Aschauer
9cc43e4166 Add MCP injection support to Jupyter backend
- start_kernel() now accepts injection_code and bridge_socket_path
- Bridge Unix domain socket mounted as volume in container
- Injection code executed once on kernel startup (silent, no history)
- New _execute_injection_code() helper method with error handling
- Parameters passed through SessionManager.create_session()
- Parameters passed through JupyterBackend.execute()
- Updated JUPYTER_IMPLEMENTATION_STATUS.md

This mirrors the MCP injection pattern from the simple executor,
allowing MCP tools to be available in Jupyter sessions.
2026-02-07 08:13:40 +01:00
Hans Aschauer
ed58c6ad5a Add Jupyter implementation status document
- Comprehensive status of real Jupyter backend implementation
- Architecture decisions documented (1:1 mapping)
- Completed features and remaining TODOs
- Test status and known issues
- Next steps prioritized
- Architecture diagrams and communication flow
2026-02-07 08:09:07 +01:00
Hans Aschauer
244a3e5574 Implement real Jupyter backend with jupyter-client
- Replaced mock exec() implementation with real Jupyter protocol
- Uses jupyter-client (host) to connect to ipykernel (container) via ZMQ
- 1:1 mapping: one container per session, one kernel per container
- Proper Jupyter message protocol for code execution
- Kernel lifecycle management (start, execute, shutdown, restart)
- Namespace inspection via introspection code
- Idle kernel cleanup
- Connection file management
- Backed up old implementation as kernel_old.py

TODO:
- Container image needs ipykernel installed
- Need to implement proper port mapping for ZMQ
- Need to mount connection file into container
- Add better kernel readiness check
- Implement restart_kernel properly with KernelManager
- Write tests
2026-02-07 08:06:44 +01:00
Hans Aschauer
372af75b90 initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00