[Feature] Windows sibling; independent MIT reimplementation; how should we relate?

[jarekom]

What problem are you hitting?

I'm building a Windows sibling of Let It Brew in a separate repo (not a patch to this macOS codebase). Your CONTRIBUTING.md asks for an issue before feature-scale work, so I'm opening this to agree scope and positioning before any PR or public claims — not to ask you to implement Windows inside this repo.

Situation: On Windows, the PC can idle-sleep while a local Claude Code or Codex session is still Working (no keyboard/mouse input for a long stretch). Generic keep-awake tools and “sleep off forever” don't follow agent lifecycle. Let It Brew on Mac already solves this with hooks; I want the same product contract on Windows as an independent MIT reimplementation.

What I need from you: Your preference on how (or whether) the projects should be linked publicly — README link, blessed unofficial sibling, or full distance. I don't want to imply endorsement you didn't give, and I don't want to open a surprise Windows PR here.

What does Let It Brew do today?

On macOS today (as I understand from the README and docs/ARCHITECTURE.md):

• Menu-bar app that observes local Claude Code and Codex via lifecycle hooks only (not timers, not process sniffing).
• Holds the Mac awake only while at least one observed session is Working, subject to safety gates (pause, battery floor, thermal when trustworthy).
• Releases when work stops — no idle-grace window.
• Can support closed-lid holding via a privileged background path, with restore exact prior sleep baseline (never force a default if baseline unreadable).
• Tray UI: three presentations only; Working sessions visible; no notification permission spam.
• Deliberately no power modes, idle-grace timers, or activity-display tuning — that restraint is the product.

What I tried on Windows (not in this repo): Sleep enabled + local agents → PC still idle-sleeps during long unattended tool runs. That's the gap I'm addressing in my own Windows repo, mirroring the Mac behavior contract rather than inventing a generic keep-awake utility.

What behavior would you expect instead?

No change to the macOS app — I'm not asking for new Mac settings, power modes, or daemon behavior.

What I'm asking instead is maintainer alignment on the Windows sibling as a separate project:

Option	Meaning
A. README link only	I ship independently; you're OK with a short "unofficial Windows sibling" link in your README (or I only link to you from my README).
B. Blessed unofficial port	You're OK with "unofficial but maintainer-aware" wording and reciprocal links; still separate repo, signing, and releases.
C. Nothing / no affiliation	I keep full distance — no README link, no implied endorsement; I only cite MIT + behavior parity in my own docs.

My Windows repo (when public): https://github.com/jarekom/let-it-brew-win
Stack there is .NET 8 WPF tray + hook CLI + elevated helper for closed-lid — not Swift/Xcode and not a PR into this tree.

I'm happy to adjust disclaimer/copy to match whatever you prefer. I will not open a Windows codebase PR against this repository unless you explicitly want that after this discussion (I expect the answer is no).

Would this need a new user-facing setting?

No — it should be automatic

Any effect on sleep, power, or the background service?

New user-facing setting (macOS): No. I'm not proposing any change to the Mac app or its Settings.

Effect on sleep, power, or the background service (macOS): None. This issue is only about how an independent Windows repo should relate to this project (README link / blessed unofficial / no affiliation). Sleep and power behavior on Windows would live entirely in the separate Windows repo, not in this codebase or its background service.

[ruban-24]

Hi Jarek,

Thanks for the thoughtful writeup, and for going through the issue process on this, appreciate it.

Let's go with Option A. Once your repo is public, we'll each add a short README link: "Windows sibling" from mine, "macOS original" from yours, purely for discoverability so users searching for the other platform can find it.

To keep expectations clear on both sides: no cross-support. Separate releases, signing, and issue trackers. Two independent MIT projects that solve the same problem on different platforms.

Send the link once it's live and I'll add the README entry and close this out.