iloom is only tested on Mac. It will probably somewhat work on linux, and maybe WSL. Windows is anyone's guess. #256
Description
Diagnostic Information
| Property | Value |
|---|---|
| CLI Version | 0.2.0 |
| Node.js Version | v22.17.0 |
| OS | darwin |
| OS Version | 24.3.0 |
| Architecture | arm64 |
| Capabilities | cli |
| Claude CLI Version | 2.0.55 (Claude Code) |
iloom is only tested on Mac. It will probably somewhat work on linux, and maybe WSL. Windows is anyone's guess.
Enhancement Request Analysis
Questions for Reporter
| Question | Answer |
|---|---|
| What specific platforms and OS versions are important for your use cases (e.g., Ubuntu 22.04, Windows 11, WSL 2)? | @acreeger, to reply, please edit this issue to answer these questions. |
| Are there specific iloom features that are critical for cross-platform support (e.g., database branching with Neon, Claude CLI integration, dev server management)? | |
| What development environments do your team members use (native Linux, WSL, Windows with Git Bash, Docker containers)? |
Problem Summary
iloom currently lacks comprehensive cross-platform testing and support documentation, limiting adoption for teams using diverse development environments beyond macOS.
User Impact
Development teams with mixed OS environments (Linux/Windows/WSL) cannot confidently adopt iloom, forcing macOS-only teams or requiring workarounds that may break unexpectedly.
Enhancement Goal
Establish official cross-platform support with comprehensive testing, platform-specific installation guides, and clear documentation of any OS-specific limitations or requirements.
Next Steps
- Reporter to answer questions above for full context
- Audit platform-specific code sections (ProcessManager, terminal integration, file paths)
- Establish CI/CD matrix testing across macOS, Linux, and Windows environments
📋 Complete Context & Details (click to expand)
Current Behavior
Based on the codebase analysis, iloom has platform-specific code in several areas:
- ProcessManager (
src/lib/process/ProcessManager.ts): Has Windows and Unix-specific implementations for port detection and process termination - Terminal Integration: iTerm2 support is macOS-only
- VS Code Integration: Should work cross-platform but untested
- File paths: Uses Node.js path module which handles cross-platform paths
- Shell commands: Mix of Unix-specific commands (lsof, kill) and Windows alternatives (netstat, taskkill)
Proposed Solution
- Immediate: Create platform compatibility matrix documenting tested vs. untested features
- Short-term: Add GitHub Actions CI/CD testing on Ubuntu and Windows runners
- Medium-term: Implement platform-specific adapters for terminal integration
- Long-term: Consider Docker-based development environments for consistent cross-platform experience
Key areas requiring platform-specific handling:
- Port detection and process management
- Terminal emulator integration (iTerm2 alternatives for Linux/Windows)
- Shell command execution patterns
- Symbolic link creation for CLI tools
- Environment variable handling
Benefits
- Enables adoption by teams with diverse development environments
- Reduces support burden by clearly documenting platform limitations
- Increases project credibility with comprehensive platform support
- Facilitates contribution from developers on all major platforms