Petal is an open-source screensharing and remote-control tool designed specifically for pair programming. Its core design bet: shared windows should behave like real windows on your desktop — movable, resizable, sharp — rather than compressed video tiles trapped inside a browser tab. The tool supports labeled multi-user cursors, instant remote mouse and keyboard input, and simultaneous window sharing by multiple users. The deployment model runs three tiers. Petal Cloud is zero-config: download, join, done, hosted on their LiveKit video infrastructure. Self-host runs the same app pointed at your own LiveKit server via a single docker-compose, keeping all media traffic internal. Fork-and-build gives full source access to rebuild everything from scratch. Currently available for Mac and Windows, with Linux support listed as coming next. The persistent-room model is the most interesting architectural choice. Rooms like "eng-sync" persist — click once and you're in, no links to send, nothing to schedule. This eliminates the scheduling-and-linking ritual that plagues every Zoom/Meet/Teams call and makes ad-hoc pairing frictionless. It's a workflow bet, not just a technology bet. Petal's generative potential hinges on whether native-window screensharing actually changes pairing behavior. The existing tools — VS Code Live Share, Tuple, Pop, even plain Zoom screenshare — all work "well enough" for most teams. Petal's argument is that the quality gap between "well enough" and "native feel" is the difference between pairing occasionally and pairing by default. That's a real hypothesis but an unproven one. The open-source angle is load-bearing. By releasing source and offering self-hosting, Petal sidesteps the trust problem that kills adoption of collaboration tools in regulated industries (finance, healthcare, defense contracting). Data-sovereignty teams that would never route screenshare traffic through a third party can run the whole stack internally. This is a genuine resilience contribution to the tooling ecosystem. The risk profile is straightforward: Petal is a small open-source project competing against tools backed by Microsoft (VS Code Live Share), Slack/Salesforce (Huddles), and Google (Meet). LiveKit dependency means the "self-host" story is only as good as LiveKit's open-source story. If LiveKit changes licensing or degrades the open tier, Petal's self-host promise erodes. The 20-year question is whether native-window screensharing becomes table stakes for all collaboration tools — in which case Petal is an early mover that gets absorbed or outcompeted — or whether it remains a niche preference for pairing-heavy teams. Either way, the open-source release means the ideas propagate even if the project doesn't survive.
