Skip to content

feat: native Windows support — run without Docker#45

Open
lhq1363511234-arch wants to merge 1 commit into
CloakHQ:mainfrom
lhq1363511234-arch:feature/windows-native-support
Open

feat: native Windows support — run without Docker#45
lhq1363511234-arch wants to merge 1 commit into
CloakHQ:mainfrom
lhq1363511234-arch:feature/windows-native-support

Conversation

@lhq1363511234-arch

Copy link
Copy Markdown

Add native Windows desktop support so CloakBrowser Manager can run directly on Windows without Docker or KasmVNC.

Changes:

  • database.py: platform-aware data directory (Windows uses %LOCALAPPDATA%)
  • vnc_manager.py: detect KasmVNC availability; graceful no-op on Windows
  • browser_manager.py: skip VNC setup on Windows, use native window + HW GL
  • main.py: handle missing VNC in WebSocket proxy and clipboard endpoints
  • ProfileViewer.tsx: show 'Browser running on desktop' when VNC unavailable
  • run.bat/run.py: one-click Windows launcher (auto-installs deps + builds)
  • New: comprehensive Chinese tutorial

Backward compatible — Docker/Linux workflow unchanged.

Add native Windows desktop support so CloakBrowser Manager can run
directly on Windows without Docker or KasmVNC.

Changes:
- database.py: platform-aware data directory (Windows uses %LOCALAPPDATA%)
- vnc_manager.py: detect KasmVNC availability; graceful no-op on Windows
- browser_manager.py: skip VNC setup on Windows, use native window + HW GL
- main.py: handle missing VNC in WebSocket proxy and clipboard endpoints
- ProfileViewer.tsx: show 'Browser running on desktop' when VNC unavailable
- run.bat/run.py: one-click Windows launcher (auto-installs deps + builds)
- New: comprehensive Chinese tutorial

Backward compatible — Docker/Linux workflow unchanged.
@lhq1363511234-arch

Copy link
Copy Markdown
Author

xixi

@Cloak-HQ

Copy link
Copy Markdown
Contributor

Thanks for this — really nice work, and clearly a lot of thought went into it. Running the Manager natively on Windows without Docker/KasmVNC is a direction we genuinely like, and the implementation is clean: gating VNC behind an availability check and falling back to native windows is the right approach, and we appreciate that the Docker/Linux path stays untouched.

We're heads-down on other priorities at the moment, so we won't be able to fully review and merge it right away — but we definitely want to come back to it when we have the bandwidth. We'll leave it open as a tracking PR.

Thanks again for the contribution. Let us know if you have any questions in the meantime!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants