Conversation
Restore the public core to the OSI-approved GNU AGPL-3.0-or-later (genuine open source) and offer a separate commercial license for uses the AGPL does not grant (proprietary embedding, closed hosted service). The AGPL-forcing RKNN dependency has been removed from the tree, and the contributor CLA already grants the relicensing right, so the dual-license is clean. - LICENSE: taOS Sustainable Use License v0.1 -> GNU AGPL-3.0-or-later (full text) - COMMERCIAL-LICENSE.md: new, explains the commercial option + contact - README + CONTRIBUTING: license sections updated to AGPL + commercial
chore(license): dual-license as AGPL-3.0-or-later + commercial
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Warning Review limit reached
Next review available in: 12 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
👋 Thanks for the PR! This one targets See CONTRIBUTING.md for the branch model. |
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| - **Self-hosted agents and chat.** Your agents, their conversations, and your channels run on hardware you control. | ||
| - **Your compute, your models.** A local model catalog and cluster inference on your own devices; cloud models are opt-in, never required. | ||
| - **Auditable and exit-able.** Source-available, with a self-hostable binary mirror and an air-gapped install path. Nothing locks you in. | ||
| - **Auditable and exit-able.** Open source (AGPL-3.0), with a self-hostable binary mirror and an air-gapped install path. Nothing locks you in. |
There was a problem hiding this comment.
WARNING: License version inconsistency. This line says Open source (AGPL-3.0) while every other reference in this PR (README line 792, CONTRIBUTING.md, COMMERCIAL-LICENSE.md) consistently says AGPL-3.0-or-later. The project license permits "or later", so dropping that qualifier here is misleading — readers may believe only v3.0 is granted.
| - **Auditable and exit-able.** Open source (AGPL-3.0), with a self-hostable binary mirror and an air-gapped install path. Nothing locks you in. | |
| - **Auditable and exit-able.** Open source (AGPL-3.0-or-later), with a self-hostable binary mirror and an air-gapped install path. Nothing locks you in. |
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| taOS is open source under the [GNU Affero General Public License v3.0 or later](LICENSE) (AGPL-3.0-or-later). | ||
|
|
||
| Free to use, modify, and self-host for personal use and for your own organisation's internal business purposes -- forever. A separate commercial license from jaylfc is required to sell taOS, host it as a paid service, or build it into a product or service you monetise (contact info@taos.my). Prior releases tagged under AGPL-3.0 remain available under AGPL-3.0. | ||
| You may use, modify, and self-host taOS freely under the AGPL, including for your own organisation's internal business purposes. The AGPL's one condition for network use is that if you run a modified taOS as a service for others, you make your modified source available to those users, also under the AGPL. |
There was a problem hiding this comment.
SUGGESTION: Imprecise wording. "you make your modified source available" reads awkwardly and "your modified source" is the wrong antecedent — the AGPL requires that the network user be offered the complete corresponding source of the modified version running there, not "your" source as a personal possession.
| You may use, modify, and self-host taOS freely under the AGPL, including for your own organisation's internal business purposes. The AGPL's one condition for network use is that if you run a modified taOS as a service for others, you make your modified source available to those users, also under the AGPL. | |
| You may use, modify, and self-host taOS freely under the AGPL, including for your own organisation's internal business purposes. The AGPL's one condition for network use is that if you run a modified taOS as a service for others, you make the complete corresponding source of that modified version available to those users, also under the AGPL. |
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| Free to use, modify, and self-host for personal use and for your own organisation's internal business purposes -- forever. A separate commercial license from jaylfc is required to sell taOS, host it as a paid service, or build it into a product or service you monetise (contact info@taos.my). Prior releases tagged under AGPL-3.0 remain available under AGPL-3.0. | ||
| You may use, modify, and self-host taOS freely under the AGPL, including for your own organisation's internal business purposes. The AGPL's one condition for network use is that if you run a modified taOS as a service for others, you make your modified source available to those users, also under the AGPL. | ||
|
|
||
| A separate **commercial license** is available from jaylfc for anyone who wants to use taOS on terms the AGPL does not grant them -- for example embedding it in a proprietary product, or offering it as a hosted or managed service without releasing modifications under the AGPL. See [COMMERCIAL-LICENSE.md](COMMERCIAL-LICENSE.md) or contact info@taos.my. |
There was a problem hiding this comment.
WARNING: Information regression in the License section. The previous README explicitly noted "Prior releases tagged under AGPL-3.0 remain available under AGPL-3.0." That clarification is dropped in this rewrite. Anyone evaluating the project or its history (especially given the prior source-available license change) will reasonably ask whether older releases are still under AGPL-3.0. Consider preserving the note, e.g. appending: "Releases previously tagged under AGPL-3.0 remain available under that license."
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| ## License & Contributor License Agreement | ||
|
|
||
| taOS is licensed under the **taOS Sustainable Use License** (source-available, not open source; see [`LICENSE`](LICENSE)) — free to use, modify, and self-host for personal use and for your own organisation's internal business purposes, with a separate commercial license required to sell it, host it as a paid service, or build it into a product you monetise. | ||
| taOS is open source under the **GNU Affero General Public License v3.0 or later** (AGPL-3.0-or-later; see [`LICENSE`](LICENSE)). A separate commercial license is available from jaylfc for uses the AGPL does not grant, for example embedding taOS in a proprietary product or offering it as a hosted service without releasing your modifications under the AGPL (see [`COMMERCIAL-LICENSE.md`](COMMERCIAL-LICENSE.md)). |
There was a problem hiding this comment.
WARNING: Contributor-facing messaging regression. The previous text explicitly reassured contributors that "you keep ownership of your work". The new text focuses only on the relicensing right granted to jaylfc. For a CLA-driven dual-license model this reassurance is the single most important contributor-facing sentence and removing it changes how the CLA reads at a glance. Recommend restoring the ownership clause, e.g. "...The CLA grants jaylfc the right to include and **relicense** your contributions under the project's licenses; **you keep ownership of your work**."
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (4 files)
Fix these issues in Kilo Cloud Reviewed by minimax-m3 · Input: 31.7K · Output: 5.2K · Cached: 336.4K |
1 participant
Promote the AGPL-3.0-or-later dual-license (PR #1721) to master so GitHub detects taOS as open source on the default branch. Docs-only: LICENSE, COMMERCIAL-LICENSE.md, README, CONTRIBUTING.