Before agents this was never an issue. But once Claude Code plugged into my dev workflow, I needed things more parallel: several agents working on the same plug-in project and they boot up Rhino to test their work autonomously, each on its own Git worktree, and they fight over which build Rhino should load.
So I built a toy project to solve this: Rhino Worktree Launcher.
The idea is simple: you pick the worktree from a small UI, or the agent picks it itself over MCP (one click in Settings hooks it up to Claude Code). It builds that worktree, temporarily registers the exact .rhp, starts Rhino, and actually checks that the process loaded that file before calling it a success. Your registry gets restored afterward, so normal Rhino sessions are untouched. The fun part: you can have several Rhinos open at once, each running a different build, and it can tell you which is which.
Windows and Rhino 8 only for now. It scratches my own itch, but if anyone else is doing parallel agent work on plug-ins, I’d love to hear if it works for your setup too.
