- SignalDesk2 hr ago
Original Summary
Hey, I recently continued the open-source OpenOwl project and rebranded it as Open Eyes by Move Weight. Repo: https://github.com/BlizzHacker/open-eyes Background OpenOwl (by Mihir Kanzariya) was an MCP server that gave AI assistants real eyes + hands on your desktop — screenshots, OCR, accessibility tree, clicking, typing, window management, workflow recording, etc. Solid foundation under Apache-2.0. I picked it up, kept full attribution (LICENSE + NOTICE still credit the original), and evolved it into Open Eyes. Same spirit: local-first desktop control for MCP clients, no cloud screen streaming required. What Open Eyes is right now Windows-focused vision + control MCP server Live screenshots (for vision models), RapidOCR, pywinauto accessibility Clicking, typing, window management, repeatable workflows Runs as a normal process on the Windows machine that has the screen and input devices Hermes can launch it persistently over local stdio Optional token-protected Streamable HTTP endpoint so something like Open WebUI on a trusted server can talk to it (private network / VPN only — don’t expose it to the internet) Quick install: PowerShell $runtime = "$env:LOCALAPPDATA\MoveWeight\OpenEyes" py -3.12 -m venv $runtime & "$runtime\Scripts\python.exe" -m pip install --no-cache-dir "open-eyes-by-moveweight[windows] @ git+https://github.com/BlizzHacker/open-eyes.git" hermes mcp add open-eyes --command "$runtime\Scripts\open-eyes.exe" My take on the “takeover” I didn’t want another abandoned or half-maintained computer-use MCP. The original work was good enough that it deserved to keep living and get tighter integration with tools people actually use day-to-day (Hermes, Open WebUI, etc.). So I: Rebranded cleanly while preserving every original copyright/notice Added the Hermes stdio + protected HTTP paths Kept the Windows console alias story sane (open-eyes while still being compatible) Focused on making the Windows experience practical (signed-in unlocked desktop, UAC realities, firewall discipline for the remote endpoint) It’s still early (0.2.0). Attribution stays rock-solid. If the original author or community wants to collaborate or correct anything, the door is open — that’s the whole point of Apache-2.0. If you’re already running local agents that need to see and act on a real Windows desktop instead of a sandboxed browser, give it a spin and tell me what breaks. Issues and PRs welcome.   submitted by   /u/Super_Classroom_8480 [link]   [comments]
- 情报分类:商业与市场研究
- 分类依据:内容涉及商业、投资或市场动态
- 信息来源:Reddit · SideProject
- 发布时间:2026/10/12 13:01:52
- No replies yet