Omahub
← All plugins
R

Simfarm

by ryuhzk

Watch and drive the iOS, Android, and WeChat simulators running on a Mac, from the Omarchy bar.

GitHub

Security review

No obvious issues detected

Deterministic scan — not a security guarantee

None
Risk level
None
Analyzed commit
5340c4e
Scanned
1 month ago

No potentially dangerous behavior detected in the analyzed commit.

Automated analysis only — not a security guarantee.

AI advisory review

Review recommended

Language-model assessment · ~deepseek/deepseek-v4-flash-latest — advisory only

Low
AI risk level
Low
Recommendation
review
Model
~deepseek/deepseek-v4-flash-latest
Analyzed commit
5340c4e
Reviewed
1 month ago

The deterministic scan found nothing, and I found no obfuscation, hidden persistence, or destructive install/remove behavior. The plugin transparently opens an SSH tunnel and a dedicated Chromium profile to a user-chosen simfarm server, and its main exposure—an unauthenticated localhost debugging port and an unauthenticated simulator stream while the panel is open—is real but documented and time-limited. I would not call it malicious, but the CDP/SSH surface is worth a quick human confirmation before publishing.

  • bin/simfarm-open launches Chromium with --remote-debugging-port set to LOCAL_PORT+1000, bound to localhost with no authentication; while the panel is open, any same-user local process can drive that browser instance over CDP, and depending on Chromium's origin checks the remote panel page may be able to as well.
  • For a plain-http simfarm URL, ssh -L exposes the unauthenticated simfarm service on 127.0.0.1:port; the README explicitly warns that any local plain-http page can watch and type into the simulator while the tunnel is up, which is a genuine privacy exposure the user must accept.
  • simfarm-theme trusts the debug-port and panel.pid files under the XDG state directory; a same-user actor who can replace those files could redirect the CDP connection, though that already implies local compromise.
How this check works

This review combines the deterministic scan (the rule-based results above) with an independent look at the plugin's code by a language model. The model reads a trimmed sample of the repository's files, the manifest, and the README, then gives a plain-language risk level and a recommendation: install (no notable danger), review (look closer first), or avoid (clearly dangerous).

It runs on the same analyzed commit as the deterministic scan and is strictly advisory — it is not a security guarantee and never blocks a plugin by itself. A human moderator still reviews plugins before they are listed.

AI advisory only — automated analysis, not a security guarantee.

Install
$ omarchy plugin add https://github.com/ryuhzk/omarchy-simfarm --enable
Developer Tools #bar #quickshell

Omarchy Simfarm

Watch and drive the iOS, Android, and WeChat simulators running on a Mac, from the Omarchy bar. The widget shows how many devices are booted; clicking opens a floating panel that streams one of them and takes your clicks and keystrokes.

<p align="center"> <img src="preview.png" alt="The panel showing an iOS simulator" width="380"> </p> <p align="center"> <a href="docs/preview.mp4">▶ Watch it being driven</a> (11s) </p>

The plugin is the way in. The streaming, the input, and the panel itself come from simfarm running on the Mac.

Features

  • One click from the bar to a floating panel showing a booted simulator.
  • Each device drawn at its real size — one device point to one screen pixel, so a 17pt label looks 17pt. Zoom out when it does not fit.
  • Hardware keys, typing (Chinese included), rotation, and a device picker that connects on selection. A device that is off gets a Start button.
  • The panel wears the current Omarchy theme and follows it when you switch, including light and dark on devices that can change appearance.
  • Nothing is connected while the panel is closed. The tunnel lives exactly as long as the window, and the widget is a launcher until you open one — no polling a Mac nobody is looking at. Open, the tooltip carries the booted count. The widget stays hidden until it is pointed at a Mac.

Requirements

  • Omarchy Shell with third-party plugin support
  • A Mac running simfarm, reachable from this desktop
  • chromium, ssh, curl, and node on the desktop
  • For a plain http:// simfarm address: key-based SSH to that Mac (the tunnel runs non-interactively, so password prompts fail closed). Not needed when simfarm is served over HTTPS.

Install

omarchy plugin add https://github.com/ryuhzk/omarchy-simfarm --enable --yes

Or from a local clone:

omarchy plugin validate ~/path/to/omarchy-simfarm
omarchy plugin add file://$HOME/path/to/omarchy-simfarm --enable --yes

Remove

omarchy plugin remove ryuhzk.simfarm

This unregisters the plugin and deletes its installed files. Three things live outside it and are left alone:

  • the widget's settings in ~/.config/omarchy/shell.json
  • the window rule, if you added one to ~/.config/hypr/hyprland.lua
  • the theme hook, if you installed one — remove it with rm ~/.config/omarchy/hooks/theme-set.d/theme-set

Its own state (~/.local/state/simfarm) and browser profile (~/.local/share/simfarm) can go too. Nothing was installed on the Mac.

Pointing it at a Mac

Open Setup › Plugins › Simfarm and set the simfarm URL. The panel needs a secure origin, because that is the only place browsers expose the video decoder. Two ways to have one:

  • Serve simfarm over HTTPS and give that URL. Tailscale HTTPS, a reverse proxy with a certificate, anything with TLS. Nothing is tunnelled.
  • Give a plain http:// URL and an SSH host. A tunnel is opened on demand so the panel loads from 127.0.0.1, which browsers also trust.

Getting this wrong is quiet rather than loud: the socket connects, the server streams, and the picture sits on its first frame.

Letting the panel float

The panel is sized to the device, which only means anything if the window is floating. Add to the bottom of ~/.config/hypr/hyprland.lua:

o.window({ class = "^chrome-.*__-Simfarm$" }, {
  float = true,
  center = true,
  size = { 500, 1040 },
})

Chromium builds the class from the origin's host and the profile directory. The host half varies with how you reach the panel, which is why it is wildcarded; the profile half is this plugin's alone, so the rule moves no other window.

Following theme changes while open

omarchy hook install theme-set ~/.config/omarchy/plugins/ryuhzk.simfarm/hooks/theme-set

Without it the panel still picks up the theme each time it opens.

What stays connected

Nothing, once the panel is closed.

Opening the panel starts the ssh tunnel (for a plain http:// address) and the launcher stays alive alongside the window. Close the window and the launcher takes the tunnel down with it. While no window is open the bar widget does not reach the network at all — it reads a local file, sees there is no panel, and says "click to open the panel". The booted count appears in the tooltip only while a panel is up.

A tunnel that was already listening on the port when the panel opened is left alone on the way out — it belongs to something else.

Settings

Key Default Description
serverUrl (empty) Where simfarm is reachable, https://… or http://…
sshHost (empty) ssh target for the tunnel; only for a plain http:// URL
localPort 8801 This end of the tunnel; ignored for https
refreshIntervalSec 20 How often the bar re-reads the booted count

Diagnosing

Open the panel from a terminal to see why it will not start:

~/.config/omarchy/plugins/ryuhzk.simfarm/bin/simfarm-open \
  --url http://<addr>:8801 --ssh <user@host> --local-port 8801

Print the theme the panel would be given:

~/.config/omarchy/plugins/ryuhzk.simfarm/bin/simfarm-theme --print

Logs live in ~/.local/state/simfarm/ — tunnel.log and browser.log.

Development

omarchy plugin validate .
omarchy restart shell     # reloads plugin code and rebuilds the bar

Saving a file under ~/.config/omarchy/plugins/ usually reloads it, but a git pull does not always trip the watcher — restart the shell if a change does not show up.

Security notes

  • The tunnel is an ordinary ssh -L to a host you name, with ExitOnForwardFailure so a taken port fails loudly instead of forwarding nowhere. Nothing is installed on the Mac.
  • The panel runs in its own browser profile, so it shares no cookies or sessions with your normal browsing.
  • simfarm itself has no authentication. Reach it over Tailscale or an SSH tunnel; do not expose it to a network you do not control.
  • A tunnel bounds which machines can reach simfarm, not which pages. It checks no Origin and asks for no credentials, so while the tunnel is up, any plain-http:// page open in any browser on this machine can open the same socket, watch the simulator and type into it. Verified, not theoretical. HTTPS pages cannot — browsers refuse ws:// from a secure page — so the exposure is plain-HTTP pages and anything able to tamper with one. It is part of why the tunnel now closes with the panel window rather than staying up.
  • The theme bridge opens a Chromium debugging port bound to localhost, used only to push theme values into the open panel.

License

MIT