Skip to content

Dodaios is an open-source agent OS for your desktop: it runs your coding agents, browser and apps by voice or chat, on your own machine. Formerly Personal Jarvis.

chore(license)!: switch from MIT to Apache 2.0

rubenluetke10-beep0166b97e5b11
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 0337a24d0c..f340dd69dc 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -85,6 +85,5 @@ the same evidence as a new speech provider, and we do not pretend otherwise.
<!--
First PR here? You do not need to get every box right. Open it, and we will
help you finish it in review. By contributing you agree your work is licensed
-under the MIT License for the 1.x line, and under the Apache License 2.0 from
-version 2.0 on — see docs/licensing.md.
+under the Apache License 2.0 — see docs/licensing.md.
-->
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 70fca2c499..6f3007eccc 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -44,13 +44,14 @@ versioning per [SemVer](https://semver.org/).
### Changed
-- **License: Apache 2.0 from version 2.0 on.** Personal Jarvis stays MIT for
- the whole 1.x line; **2.0.0** switches to the Apache License 2.0 — the same
- freedoms, plus an explicit patent grant and a written trademark carve-out.
- The full text is already in the repository as `LICENSE-APACHE-2.0` so the
- terms can be read before they apply, and `docs/licensing.md` says what
- changes for users, forks, and contributors. Nothing already published
- changes: a copy obtained under MIT stays MIT.
+- **License: Apache 2.0.** `LICENSE` is the Apache License 2.0 and `NOTICE`
+ sits beside it — the same freedoms MIT gave, plus an explicit patent grant
+ from every contributor and a written trademark carve-out. It takes effect
+ with the next release, **2.0.0**; a license change is a breaking change, so
+ there is no further 1.x. Every release up to and including 1.6.0 stays MIT
+ permanently — that cannot be revoked, and a copy taken under MIT keeps
+ those rights. `docs/licensing.md` says why, what it changes for users,
+ forks, and contributors, and what nobody has to go back and correct.
- **README: the hero screenshot is the current home view.** The old
wallpaper-and-mascot capture is replaced with a live voice conversation
in the desktop app.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f65d31d2b1..79b37bbdaf 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -15,7 +15,7 @@
<a href="https://github.com/PersonalJarvis/PersonalJarvis/pulls"><img alt="PRs welcome" src="https://img.shields.io/badge/PRs-welcome-FFD60A?style=flat-square&labelColor=0A0A0A" /></a>
<a href="https://github.com/PersonalJarvis/PersonalJarvis/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22"><img alt="Good first issues" src="https://img.shields.io/badge/good%20first%20issues-open-FFD60A?style=flat-square&labelColor=0A0A0A" /></a>
<a href="https://discord.gg/x7USduHxbc"><img alt="Discord" src="https://img.shields.io/badge/Discord-join-FFD60A?style=flat-square&logo=discord&logoColor=0A0A0A&labelColor=0A0A0A" /></a>
- <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-FFD60A?style=flat-square&labelColor=0A0A0A" /></a>
+ <a href="LICENSE"><img alt="License: Apache 2.0" src="https://img.shields.io/badge/License-Apache_2.0-FFD60A?style=flat-square&labelColor=0A0A0A" /></a>
</p>
---
@@ -123,8 +123,7 @@ Unsure which row you're in? Open the PR and ask. We'd rather tell you in review
you guess high and waste an evening.
Describe what changed and why, link the issue it closes. By contributing you agree your work
-is licensed under the [MIT License](LICENSE) for the 1.x line, and under the
-[Apache License 2.0](LICENSE-APACHE-2.0) from version 2.0 on — see
+is licensed under the [Apache License 2.0](LICENSE) — see
[`docs/licensing.md`](docs/licensing.md).
---
diff --git a/LICENSE b/LICENSE
index cf6ea44762..889adf2d6d 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,21 +1,201 @@
-MIT License
-
-Copyright (c) 2026 Ruben Lütke
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright 2026 Ruben Lütke
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/LICENSE-APACHE-2.0 b/LICENSE-APACHE-2.0
deleted file mode 100644
index a7caebea7c..0000000000
--- a/LICENSE-APACHE-2.0
+++ /dev/null
@@ -1,202 +0,0 @@
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright 2026 Ruben Lütke
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
diff --git a/NOTICE b/NOTICE
new file mode 100644
index 0000000000..cfb9bfae64
--- /dev/null
+++ b/NOTICE
@@ -0,0 +1,13 @@
+Personal Jarvis
+Copyright 2026 Ruben Lütke
+
+This product includes software developed by the Personal Jarvis contributors
+(https://github.com/PersonalJarvis/PersonalJarvis).
+
+Releases up to and including 1.6.0 were published under the MIT License and
+remain MIT. From version 2.0.0 on, this product is licensed under the Apache
+License, Version 2.0.
+
+Bundled third-party components keep their own licenses and notices - see
+docs/licensing.md and the license files shipped beside them, for example
+jarvis/assets/vad/LICENSE for the Silero VAD model.
diff --git a/README.md b/README.md
index 2979034eea..53e038b278 100644
--- a/README.md
+++ b/README.md
@@ -40,7 +40,7 @@ walks you through language, wake word, and keys once. [Full install notes below]
<p align="center">
<a href="https://pypi.org/project/personal-jarvis/"><img alt="PyPI: personal-jarvis" src="https://img.shields.io/pypi/v/personal-jarvis?style=for-the-badge&labelColor=242424&color=e7c46e" /></a>
- <a href="https://github.com/PersonalJarvis/PersonalJarvis/blob/main/LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-e7c46e?style=for-the-badge&labelColor=242424" /></a>
+ <a href="https://github.com/PersonalJarvis/PersonalJarvis/blob/main/LICENSE"><img alt="License: Apache 2.0" src="https://img.shields.io/badge/License-Apache_2.0-e7c46e?style=for-the-badge&labelColor=242424" /></a>
<a href="https://discord.gg/x7USduHxbc"><img alt="Discord" src="https://img.shields.io/badge/Discord-Join-5865F2?style=for-the-badge&logo=discord&logoColor=white&labelColor=242424" /></a>
<a href="https://personaljarvis.ai/"><img alt="Personal Jarvis website" src="https://img.shields.io/badge/Website-personaljarvis.ai-e7c46e?style=for-the-badge&labelColor=242424" /></a>
</p>
@@ -198,8 +198,8 @@ installer checks for both and stops with a download link if one is missing. It a
in the terminal. It launches the app, and the app walks you through a one-time setup for
language, wake word, and API keys.
-**What it costs: nothing to us.** Personal Jarvis is MIT-licensed software you run on your
-own machine. There is no subscription for it, no paid tier, no marketplace cut, and no
+**What it costs: nothing to us.** Personal Jarvis is open-source software (Apache 2.0) you run
+on your own machine. There is no subscription for it, no paid tier, no marketplace cut, and no
referral link behind any provider named on this page. What you do need is access to a
model, and that is billed by whoever provides it, straight to you. An AI subscription you
already pay for works, and so does a pay-per-token API key. The same goes for the optional
@@ -639,14 +639,14 @@ the same day on [Discord](https://discord.gg/x7USduHxbc).
## License
-MIT. Free to use, modify, and distribute, including commercially; see
-[`LICENSE`](https://github.com/PersonalJarvis/PersonalJarvis/blob/main/LICENSE).
+Apache 2.0. Free to use, modify, and distribute, including commercially, with an
+explicit patent grant from every contributor; see
+[`LICENSE`](https://github.com/PersonalJarvis/PersonalJarvis/blob/main/LICENSE) and [`NOTICE`](https://github.com/PersonalJarvis/PersonalJarvis/blob/main/NOTICE).
-**From version 2.0 on, Personal Jarvis moves to the Apache License 2.0** — the same
-freedoms, plus an explicit patent grant and a written trademark carve-out. The text
-is already in the repository as [`LICENSE-APACHE-2.0`](https://github.com/PersonalJarvis/PersonalJarvis/blob/main/LICENSE-APACHE-2.0)
-and [`docs/licensing.md`](https://github.com/PersonalJarvis/PersonalJarvis/blob/main/docs/licensing.md) says what changes for users,
-forks, and contributors. Every 1.x release stays MIT, permanently.
+Personal Jarvis was MIT-licensed through version 1.6.0, and **every one of those
+releases stays MIT, permanently** — the switch applies from 2.0 on.
+[`docs/licensing.md`](https://github.com/PersonalJarvis/PersonalJarvis/blob/main/docs/licensing.md) says why, and what it changes for
+users, forks, and contributors.
Third-party names and logos belong to their owners,
see [`TRADEMARK.md`](https://github.com/PersonalJarvis/PersonalJarvis/blob/main/TRADEMARK.md).
@@ -654,6 +654,6 @@ see [`TRADEMARK.md`](https://github.com/PersonalJarvis/PersonalJarvis/blob/main/
<br/>
<p align="center">
- <sub>Created by <b>Ruben Lütke</b> · <a href="https://x.com/Ruben_Luetke">@Ruben_Luetke</a> · © 2026 · MIT</sub><br/> <!-- i18n-allow: maintainer's name, not German prose -->
+ <sub>Created by <b>Ruben Lütke</b> · <a href="https://x.com/Ruben_Luetke">@Ruben_Luetke</a> · © 2026 · Apache 2.0</sub><br/> <!-- i18n-allow: maintainer's name, not German prose -->
<sub><a href="https://discord.gg/x7USduHxbc">Discord</a> · <a href="https://x.com/Ruben_Luetke">X</a> · <a href="https://www.instagram.com/personaljarvis/">Instagram</a></sub>
</p>
diff --git a/assets/brand/social-preview.html b/assets/brand/social-preview.html
index 432fa50044..6bef63ea48 100644
--- a/assets/brand/social-preview.html
+++ b/assets/brand/social-preview.html
@@ -72,7 +72,7 @@
</div>
<img class="wordmark" src="banner.png" alt="Personal Jarvis" />
<div class="tagline">Talk to your computer — <span class="gold">and watch it do the work.</span></div>
- <div class="meta">OPEN SOURCE · MIT · LINUX · MACOS · WINDOWS</div>
+ <div class="meta">OPEN SOURCE · APACHE 2.0 · LINUX · MACOS · WINDOWS</div>
</div>
</body>
</html>
diff --git a/docs/LLM-CONTEXT.md b/docs/LLM-CONTEXT.md
index f0d3ff3dff..1807c801a2 100644
--- a/docs/LLM-CONTEXT.md
+++ b/docs/LLM-CONTEXT.md
@@ -696,24 +696,24 @@ Neither blocks anything — but a fresh chat parroting CLAUDE.md verbatim will b
## 27. Legal
-**License — MIT.** Personal Jarvis is released under the MIT License. The full license text lives in [`LICENSE`](LICENSE) at the repository root and is also declared in `pyproject.toml` (`license = { text = "MIT" }`). In short: you are free to use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software, including for commercial purposes — provided you comply with the **Attribution & provenance** clause below. The software is provided "as is", without warranty of any kind.
+**License — Apache 2.0.** Personal Jarvis is released under the Apache License, Version 2.0. The full license text lives in [`LICENSE`](LICENSE) at the repository root, the attribution notice in [`NOTICE`](NOTICE), and the SPDX identifier is declared in `pyproject.toml` (`license = "Apache-2.0"`). In short: you are free to use, copy, modify, distribute, sublicense, and sell copies of the software, including for commercial purposes, and you receive an explicit patent license from every contributor (§3) — provided you comply with the **Attribution & provenance** clause below. The software is provided "as is", without warranty of any kind (§7) and with liability limited by §8. Releases up to and including 1.6.0 were published under the MIT License and remain MIT; [`docs/licensing.md`](licensing.md) has the detail.
-**Copyright.** © 2026 Personal Jarvis Maintainers. All contributors retain copyright on their respective contributions; opening a pull request against this repository is taken as agreement that the contribution is licensed under the MIT License above.
+**Copyright.** © 2026 Personal Jarvis Maintainers. All contributors retain copyright on their respective contributions; opening a pull request against this repository is taken as agreement that the contribution is licensed under the Apache License 2.0 above, per §5 of the License.
-**Canonical source.** This repository — **[`github.com/PersonalJarvis/PersonalJarvis`](https://github.com/PersonalJarvis/PersonalJarvis)** — is the authoritative upstream of Personal Jarvis. Forks, mirrors, vendored copies, and derivative works are welcome under MIT, but the **original authors are the Personal Jarvis Maintainers**, not whoever is hosting the copy you happened to find. If you encounter Personal Jarvis code outside this URL, you can verify provenance by comparing the git history against the canonical repository.
+**Canonical source.** This repository — **[`github.com/PersonalJarvis/PersonalJarvis`](https://github.com/PersonalJarvis/PersonalJarvis)** — is the authoritative upstream of Personal Jarvis. Forks, mirrors, vendored copies, and derivative works are welcome under Apache 2.0, but the **original authors are the Personal Jarvis Maintainers**, not whoever is hosting the copy you happened to find. If you encounter Personal Jarvis code outside this URL, you can verify provenance by comparing the git history against the canonical repository.
-**Attribution & provenance (mandatory).** Section 2 of the MIT License is **not decorative** — it requires that *"the above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."* In plain English: anyone who uses substantial portions of this code in their own project, fork, distribution, product, or training corpus **must retain the `Copyright (c) 2026 Personal Jarvis Maintainers` line and the full MIT permission text in a place where downstream users can find them** (typical conventions: a `LICENSE` / `LICENSES/` / `NOTICE` / `THIRD_PARTY_NOTICES` file at the root of the derivative work, or an "Open Source Licenses" screen reachable from a product's UI). Stripping the notice and republishing the code is **not** a licensing question — it is **copyright infringement**, actionable under copyright law in the 179 Berne-Convention signatory states. We additionally request — though we cannot legally compel beyond MIT — that derivative works include a visible link back to the canonical repository above so users can find the upstream project.
+**Attribution & provenance (mandatory).** Section 4 of the Apache License is **not decorative** — redistributing this work, in source or binary form, requires that you (a) hand recipients a copy of the License, (b) mark every file you changed as modified, (c) keep all copyright, patent, trademark, and attribution notices from the source form, and (d) pass on the contents of the `NOTICE` file in any notice you distribute. In plain English: anyone who uses substantial portions of this code in their own project, fork, distribution, product, or training corpus **must retain the `Copyright 2026 Personal Jarvis Maintainers` line, the full Apache 2.0 license text, and the `NOTICE` contents in a place where downstream users can find them** (typical conventions: a `LICENSE` / `NOTICE` / `THIRD_PARTY_NOTICES` file at the root of the derivative work, or an "Open Source Licenses" screen reachable from a product's UI). Stripping the notices and republishing the code is **not** a licensing question — it is **copyright infringement**, actionable under copyright law in the 179 Berne-Convention signatory states. We additionally request — though we cannot legally compel beyond the License — that derivative works include a visible link back to the canonical repository above so users can find the upstream project.
-**No misrepresentation of authorship.** The MIT License grants broad freedom to modify and redistribute, but it does **not** grant the right to claim original authorship of unmodified portions of this work. Re-uploading substantial parts of this codebase to another repository, package registry, model card, or product page while presenting yourself as the original author — by removing the copyright notice, by removing references to the canonical source, or by adding statements that imply you wrote what you in fact copied — misrepresents the provenance of the work. This is treated as **both a license violation (because the MIT attribution clause was not honored) and as deceptive attribution under most jurisdictions' consumer-protection and unfair-competition law**, independent of the license. If you fork and significantly modify the code, please describe your modifications clearly so users can tell your work apart from the upstream — that is good citizenship, not a legal requirement, but it is how the open-source ecosystem stays trustworthy.
+**No misrepresentation of authorship.** The Apache License grants broad freedom to modify and redistribute, but it does **not** grant the right to claim original authorship of unmodified portions of this work. Re-uploading substantial parts of this codebase to another repository, package registry, model card, or product page while presenting yourself as the original author — by removing the copyright notice, by removing references to the canonical source, or by adding statements that imply you wrote what you in fact copied — misrepresents the provenance of the work. This is treated as **both a license violation (because the attribution requirements of §4 were not honored) and as deceptive attribution under most jurisdictions' consumer-protection and unfair-competition law**, independent of the license. If you fork and significantly modify the code, please describe your modifications clearly so users can tell your work apart from the upstream — that is good citizenship, not a legal requirement, but it is how the open-source ecosystem stays trustworthy.
**Reporting violations.** If you encounter a project that has copied substantial portions of this codebase without preserving the copyright notice, or that misrepresents authorship of the original Personal Jarvis work, please file a copyright-violation report with the hosting platform — for GitHub, the [DMCA Takedown Policy](https://docs.github.com/en/site-policy/content-removal-policies/dmca-takedown-policy) is the standard route — or open an issue on the canonical repository. The Personal Jarvis Maintainers reserve all rights granted by copyright law.
-**Third-party software.** This project bundles, imports, or vendors a number of open-source dependencies, each governed by its own license — notably MIT (React, Vite, Zustand, TanStack Query, `pywebview`, `tomlkit`, `keyring`, `croniter`), Apache 2.0 (`faster-whisper`, `silero-vad`, `onnxruntime`, the OpenAI / Gemini / Grok / Anthropic SDKs), BSD-3-Clause (`numpy`, `sounddevice`, `mss`), and Picovoice's commercial-with-free-tier terms for `pvporcupine`. **No third-party dependency is relicensed by inclusion in this repository**, and the attribution requirement above applies to Personal Jarvis's own code, not to the upstream licenses of bundled dependencies (which carry their own attribution clauses you must also honor).
+**Third-party software.** This project bundles, imports, or vendors a number of open-source dependencies, each governed by its own license — notably MIT (React, Vite, Zustand, TanStack Query, `pywebview`, `tomlkit`, `keyring`, `croniter`, the bundled `silero-vad` model), Apache 2.0 (`faster-whisper`, `onnxruntime`, the OpenAI / Gemini / Grok / Anthropic SDKs), BSD-3-Clause (`numpy`, `sounddevice`, `mss`), and Picovoice's commercial-with-free-tier terms for `pvporcupine`. **No third-party dependency is relicensed by inclusion in this repository**, and the attribution requirement above applies to Personal Jarvis's own code, not to the upstream licenses of bundled dependencies (which carry their own attribution clauses you must also honor).
**Trademarks.** "Claude", "Anthropic", "OpenAI", "Gemini", "Grok", "Picovoice", "Porcupine", "Obsidian", "GitHub", "Windows", and any other product or company names referenced in this repository are trademarks of their respective owners and are used here for identification purposes only. Their use does not imply endorsement of this project by, or affiliation with, the trademark holder.
**Audio, voice, and screen-capture privacy disclosure.** When the `[desktop]` extras are installed, Personal Jarvis can capture microphone audio (STT), play synthesized speech (TTS), take screenshots and read UI element trees (Vision / Computer-Use), and read text from the active window. All of these capabilities are opt-in at install time and run only in the user's session. STT, TTS, and Brain calls are routed through the providers the user configures (Gemini, Grok, OpenAI, Deepgram, ElevenLabs, Google Cloud, etc.) — please review each provider's privacy policy before sending production data through them. The headless VPS base install captures no local audio and no screen content.
-**No warranty for self-modifying behaviour.** The Phase-7 self-mod tools (`set_config_value`, `spawn-skill-author`) and the Phase-6 Worker-Critic loop can write to `jarvis.toml`, generate skills (created with `state="draft"`, never auto-activated — AP-15), and create isolated `git worktree` branches under `<repo_parent>/sub-agents-outputs/`. The 10-step atomic-write pipeline (allowlist → pre-validate → backup → tempfile → synchronous reload → rollback → audit) is designed to be safe and reversible, but the MIT "as is" disclaimer applies in full: the maintainers are not liable for any state the system writes on your behalf, on your filesystem or against the third-party APIs you have configured.
+**No warranty for self-modifying behaviour.** The Phase-7 self-mod tools (`set_config_value`, `spawn-skill-author`) and the Phase-6 Worker-Critic loop can write to `jarvis.toml`, generate skills (created with `state="draft"`, never auto-activated — AP-15), and create isolated `git worktree` branches under `<repo_parent>/sub-agents-outputs/`. The 10-step atomic-write pipeline (allowlist → pre-validate → backup → tempfile → synchronous reload → rollback → audit) is designed to be safe and reversible, but the Apache 2.0 "as is" disclaimer (§7) and limitation of liability (§8) apply in full: the maintainers are not liable for any state the system writes on your behalf, on your filesystem or against the third-party APIs you have configured.
-**Contributing.** Pull requests are welcome. By contributing you agree that your contribution is licensed under the MIT License above. See [`CLAUDE.md`](CLAUDE.md) and [`CLAUDE.md`](CLAUDE.md) for the binding output-language policy (English-only artifacts) and the cloud-first design doctrine. The repository's bug register lives at [`docs/BUGS.md`](docs/BUGS.md); architecture decisions are recorded under [`docs/adr/`](docs/adr/).
+**Contributing.** Pull requests are welcome. By contributing you agree that your contribution is licensed under the Apache License 2.0 above. See [`CLAUDE.md`](CLAUDE.md) and [`CLAUDE.md`](CLAUDE.md) for the binding output-language policy (English-only artifacts) and the cloud-first design doctrine. The repository's bug register lives at [`docs/BUGS.md`](docs/BUGS.md); architecture decisions are recorded under [`docs/adr/`](docs/adr/).
diff --git a/docs/licensing.md b/docs/licensing.md
index 08452a101d..8b4187c7bf 100644
--- a/docs/licensing.md
+++ b/docs/licensing.md
@@ -1,69 +1,82 @@
# Licensing
-## Today: MIT
+## Current: Apache License 2.0
-Every release up to and including the 1.x line is licensed under the
-[MIT License](../LICENSE). That does not change retroactively, and it cannot:
-a copy obtained under MIT stays MIT forever, including the right to fork it.
+Personal Jarvis is licensed under the [Apache License 2.0](../LICENSE), with the
+attribution notice in [`NOTICE`](../NOTICE). The switch was made on `main` on
+2026-08-27 and ships with **version 2.0.0** — the first release under the new
+terms. Everything merged from that day on is Apache 2.0.
-## From version 2.0: Apache License 2.0
+Because a license change is a breaking change in SemVer terms, the next release
+out of `main` is 2.0.0. There is no further 1.x release.
-Starting with **2.0.0**, Personal Jarvis is licensed under the
-[Apache License 2.0](../LICENSE-APACHE-2.0). The full text already sits in the
-repository so the terms can be read before they apply — it is **not in force
-yet**. The file that governs the code you have today is still `LICENSE`.
+## Released 1.x stays MIT, permanently
-### Why
+Every release up to and including 1.6.0 was published under the MIT License and
+remains MIT. That cannot be revoked: a copy obtained under MIT keeps those
+rights forever, including the right to fork it. The text those releases shipped
+with is still in the history — `git show v1.6.0:LICENSE`.
+
+## Why Apache 2.0
Apache 2.0 keeps everything MIT gives you — use, modify, distribute, sell, no
copyleft, no source-sharing obligation — and closes three things MIT leaves
unsaid:
-- **An explicit patent grant** (§3). Every contributor grants users a license
- to the patents their contribution needs, and that grant ends for anyone who
- sues over them. MIT says nothing about patents at all, which is the single
- most common reason a corporate legal review rejects an MIT dependency.
+- **An explicit patent grant** (§3). Every contributor grants users a license to
+ the patents their contribution needs, and that grant ends for anyone who sues
+ over them. MIT says nothing about patents at all, which is the single most
+ common reason a corporate legal review rejects an MIT dependency.
- **A trademark carve-out** (§6). The license covers the code and not the name
or the logo, in writing. Ours already lives in
[`TRADEMARK.md`](../TRADEMARK.md); Apache 2.0 makes it a license term.
- **Stated redistribution duties** (§4). Pass on the license, keep the notices,
- mark the files you changed. MIT only asks for the copyright line.
+ carry the `NOTICE` file, mark the files you changed. MIT only asks for the
+ copyright line.
+
+## What it means for you
+
+- **Users:** nothing to do. The freedoms are the same, and you gain a patent
+ license you did not have before.
+- **Forks and redistributors:** anything you took under 1.x stays MIT. From
+ 2.0 on, ship `LICENSE` and `NOTICE` with your copies and mark the files you
+ modified.
+- **Contributors:** by opening a pull request you agree your work is licensed to
+ the project under the Apache License 2.0, per §5 of the License.
+
+## What does NOT need changing
-### What it means for you
+A license change applies going forward. It does not make past statements wrong,
+and it creates no duty to hunt them down:
-- **Users:** nothing to do. The freedoms are the same, in both directions in
- time.
-- **Forks and redistributors:** anything you took under 1.x stays under MIT.
- From 2.0 on, keep `LICENSE` and any `NOTICE` file with your copies and mark
- the files you modified.
-- **Contributors:** by opening a pull request you agree your work is licensed
- to the project under the MIT License for the 1.x line and under the Apache
- License 2.0 from 2.0 on. This is stated up front so the switch needs no
- chase-down of past authors later.
+- **Videos, talks, streams, and old posts that say "MIT".** They described the
+ releases that existed when they were recorded, and for those releases the
+ statement is still true. Leave them up. Adding a line to the description of
+ the most-watched ones ("from 2.0 on: Apache 2.0") is courtesy, not a
+ correction — taking them offline would look like something was wrong when
+ nothing was.
+- **Anything already downloaded, forked, or vendored.** It stays MIT, and no
+ one has to be told.
+- **Blog posts, press coverage, and third-party listings.** Not yours to fix.
-### Third-party components
+What does have to be current is anything that states the license **as of
+today**: this repository, personaljarvis.ai, package listings, app-store
+descriptions, and pinned posts. Those are the checklist below.
+
+## Third-party components
The bundled Silero VAD model (`jarvis/assets/vad/`) carries its own MIT license
from its own authors and keeps it — the switch does not touch it, and no
-dependency's terms change either.
-
-## Checklist for the 2.0 release
-
-Every place the license is named today, so nothing is left claiming "MIT" after
-the switch:
-
-- [ ] `LICENSE` — replace the MIT text with the contents of
- `LICENSE-APACHE-2.0`, then delete `LICENSE-APACHE-2.0`
-- [ ] `NOTICE` — add one (optional under §4d, but the conventional place for
- the attribution line downstream copies must carry)
-- [ ] `pyproject.toml` — `license = "Apache-2.0"`
-- [ ] `README.md` — the badge, the "what it costs" paragraph, the License
- section, the footer line
-- [ ] `CONTRIBUTING.md` — the badge and the contribution paragraph
-- [ ] `.github/PULL_REQUEST_TEMPLATE.md` — the contribution note
-- [ ] `jarvis.spec` — the `LegalCopyright` string in the Windows version
- resource
-- [ ] `homebrew-tap/Formula/personal-jarvis-installer.rb` — `license "Apache-2.0"`
-- [ ] `scoop-bucket/personal-jarvis-installer.json` — `"license": "Apache-2.0"`
-- [ ] `CHANGELOG.md` — record it under 2.0.0
-- [ ] this file — drop the "from 2.0" framing and state Apache 2.0 as current
+dependency's terms change either. Nothing is relicensed by being included here.
+
+## Still to do at the 2.0 release
+
+- [ ] `homebrew-tap/Formula/personal-jarvis-installer.rb` and
+ `scoop-bucket/personal-jarvis-installer.json` — both are pinned to the
+ v1.0.5 installer asset, which really is MIT. Change `license` in the same
+ commit that bumps them to the 2.0 asset, not before.
+- [ ] `assets/brand/social-preview.html` — the template says "APACHE 2.0" now;
+ re-render the PNG and upload it as the repository's social preview.
+- [ ] personaljarvis.ai (the `webui` repo) — any license mention on the
+ storefront.
+- [ ] The GitHub release notes for 2.0.0 — lead with the license change.
diff --git a/jarvis.spec b/jarvis.spec
index 0f25c87f12..a6e015f1b3 100644
--- a/jarvis.spec
+++ b/jarvis.spec
@@ -312,7 +312,7 @@ if sys.platform == "win32":
StringStruct("InternalName", GUI_EXE_NAME),
StringStruct(
"LegalCopyright",
- "Personal Jarvis contributors. MIT licensed.",
+ "Personal Jarvis contributors. Apache 2.0 licensed.",
),
StringStruct("OriginalFilename", f"{GUI_EXE_NAME}.exe"),
StringStruct("ProductName", "Personal Jarvis"),
diff --git a/pyproject.toml b/pyproject.toml
index 8fead68893..8c003840b4 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -13,11 +13,10 @@ version = "1.6.0"
description = "Voice-driven meta-orchestrator that turns one spoken request into a fleet of self-checking AI agents"
requires-python = ">=3.11,<3.15"
readme = "README.md"
-# MIT governs the whole 1.x line. Version 2.0.0 switches this to "Apache-2.0"
-# and LICENSE to the text already sitting in LICENSE-APACHE-2.0; the full list
-# of places to change lives in docs/licensing.md.
-license = "MIT"
-license-files = ["LICENSE"]
+# Apache-2.0 from 2.0.0 on. Releases up to 1.6.0 shipped MIT and stay MIT —
+# docs/licensing.md has the reasoning and what is still owed at the release.
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
authors = [{ name = "Ruben Lütke" }] # i18n-allow: maintainer proper name (umlaut)
keywords = [
"voice-assistant",
@@ -550,7 +549,7 @@ vertex-stt = "jarvis.plugins.stt.gemini_api:VertexSTT"
[project.entry-points."jarvis.tts"]
# Local, keyless neural speech (Piper VITS voices via sherpa-onnx / ONNX
# Runtime). The voices are plain ONNX files, deliberately NOT loaded through the
-# GPL-3 piper1-gpl library, so this MIT repo stays MIT.
+# GPL-3 piper1-gpl library, so this repo stays free of GPL obligations.
piper-local = "jarvis.plugins.tts.piper_local:PiperLocalTTS"
inworld = "jarvis.plugins.tts.inworld_tts:InworldTTS"
elevenlabs = "jarvis.plugins.tts.elevenlabs_tts:ElevenLabsTTS"
diff --git a/skillbook/pyproject.toml b/skillbook/pyproject.toml
index 2b0c33ef3a..511d4fb186 100644
--- a/skillbook/pyproject.toml
+++ b/skillbook/pyproject.toml
@@ -3,7 +3,7 @@ name = "skillbook"
version = "0.1.0"
description = "Recursive, decentralized learning and memory layer for AI agents (ACE + LATS + CRDT)."
requires-python = ">=3.11"
-license = { text = "MIT" }
+license = { text = "Apache-2.0" }
authors = [{ name = "Skillbook contributors" }]
dependencies = [
"numpy>=1.26",