stif1337

4 ms·

1. 1.▲
   by stif1337 7mo ago

   Update: Since the initial post, I've shipped several features based on feedback: - Screenshot capture: GET /windows/{pid}/screenshot → returns PNG - Batch operations: POST /interact/batch → multiple actions per
2. 2.▲
   by stif1337 7mo ago

   No toolkit dependency, OculOS reads the OS-level accessibility tree, which is toolkit-agnostic: - Windows: UI Automation (works with Win32, WPF, WinForms, Qt, Electron) - Linux: AT-SPI2 (GTK, Qt, Electron) - macOS: AXUIElement (Cocoa, Qt, E
3. 3.▲
   by stif1337 7mo ago

   Thanks! Python and TypeScript SDKs are high on the roadmap.
4. 4.▲
   by stif1337 7mo ago

   Yes, electron apps expose a reasonable accessibility tree through Chromium's UIA/AT-SPI bridge. We've tested with Spotify (Electron/CEF), VS Code, Slack, and Chrome itself. The tree is shallower than native Win32/WP
5. 5.▲
   by stif1337 7mo ago

   It actually supports both you can use it as a plain REST API (no MCP needed) with any HTTP client: curl localhost:7878/windows curl -X POST localhost:7878/interact/{id}/click MCP mode is an optional layer for AI
6. 6.▲
   Show HN: OculOS – Any desktop app as a JSON API via OS accessibility tree(github.com)

   18 points by stif1337 7mo ago|9 comments
7. 7.▲
   Show HN: OculOS – Give AI agents control of your desktop via MCP(github.com)

   1 points by stif1337 7mo ago|0 comments
8. 8.▲
   Show HN: OculOS – Any desktop app as a JSON API via OS accessibility tree(github.com)

   5 points by stif1337 7mo ago|0 comments