BACK_TO_FEEDAICRIER_2
OpenWork relicenses, paywalls Windows build
OPEN_SOURCE ↗
REDDIT · REDDIT// 2d agoNEWS

OpenWork relicenses, paywalls Windows build

OpenWork, the locally hosted Claude Code-style agent harness, has shifted from a straightforward MIT-only pitch toward an open-core model. The repo now carves out `/ee` under a commercial license, while Windows access is sold separately through a paid support plan.

// ANALYSIS

This looks less like a clean license clarification and more like a quiet boundary shift between “free” and “paid” parts of the stack.

  • The root `LICENSE` now says `/ee` content is covered by `ee/LICENSE`, while the rest remains MIT, so the repo is no longer uniformly MIT in practice.
  • The project site now advertises macOS and Linux as free, but Windows access is handled through a paid support plan.
  • That makes OpenWork feel like an open-core product: OSS desktop core, commercial enterprise/Windows layer, and cloud workers on top.
  • The concern for contributors is simple: the exact folder you touch now matters a lot more than it did before.
  • The bigger issue is communication; when licensing changes this materially, silence creates avoidable trust damage.
// TAGS
open-sourceself-hostedagentai-codingclimcpopenwork

DISCOVERED

2d ago

2026-04-09

PUBLISHED

3d ago

2026-04-09

RELEVANCE

8/ 10

AUTHOR

lrq3000