1. Scope and contact
These terms govern the Choro website, official Choro desktop releases, the Choro-operated Design service, and optional Choro Remote functionality. “Choro”, “we”, and “us” refer to the operator identified on the official download page and in the application’s signed distribution record.
Product questions may be sent to support@choro.dev, and legal notices to legal@choro.dev. The operator’s complete legal name and service address appear on the official download page.
2. Agreement
By downloading, installing, or using Choro after these terms are presented to you, you agree to them. If you use Choro for an organisation, you confirm that you have authority to accept these terms for that organisation.
You must have legal capacity to agree to these terms and satisfy the age and account requirements of every provider you connect. If you do not agree, do not download or use Choro.
The open-source licence described below separately gives rights to covered source code; those rights are not taken away by this website document.
3. What Choro provides
Choro is a macOS workspace that brings projects, documents, designs, Git tools, local services, databases, terminals, and coding agents into one interface. The coding workspace and agents run on the user’s computer. Choro does not currently provide a hosted model account, cloud-agent computer, or subscription to a model provider.
Choro Design is a hosted design workspace based on the open-source Penpot project. Choro automatically provisions a private Design profile for an installation so the application can create, display, and edit design files. The Design service is operated by Choro and is not the Penpot cloud service operated by Kaleidos.
Remote access is optional. When enabled, it connects an authorised device to a running Choro Desktop instance through an application-encrypted relay. The Mac remains the host and must be online.
4. Software licence
Choro-authored source code and documentation made available in the repository are licensed under the Apache License 2.0, unless a file or directory says otherwise. That licence controls your rights to use, copy, modify, and distribute the covered source and binaries.
Choro also includes third-party components under their own licences. Their notices are listed in THIRD_PARTY_NOTICES.md and, for packaged builds, in the application’s bundled licence resources. Brand names and logos for integrations belong to their respective owners.
The hosted Design service uses Penpot under the Mozilla Public License 2.0. Penpot and Choro’s modifications to MPL-covered Penpot files remain under MPL-2.0. The applicable notices and instructions for obtaining that source are on the Open source page. Those terms do not change the Apache-2.0 licence for separate Choro-authored files.
If you redistribute Apache-licensed Choro material, follow the licence itself: provide the Apache licence, preserve applicable copyright, patent, trademark, and attribution notices, retain the NOTICE attributions where required, and mark modified files prominently. Third-party components may impose additional file-level or attribution duties.
5. Third-party tools and providers
Choro can launch or display tools such as coding-agent CLIs, Git, database clients, and developer services that you install or configure. You bring your own accounts, subscriptions, API credentials, and local tools. Choro does not sell or transfer model-provider access.
Your use of any provider remains subject to that provider’s terms, acceptable-use rules, pricing, and privacy policy. Choro is not sponsored by, affiliated with, or responsible for third-party providers merely because an integration is shown in the product.
A provider may restrict how personal-plan credentials are used by third-party products. An integration is available only where its authentication method is permitted for Choro’s use case. A statement in Choro’s own terms cannot override a provider’s rules.
6. Your content and permissions
You keep ownership of your projects, prompts, documents, designs, repositories, credentials, and other content. You give Choro the permissions needed to provide actions you request—for example, reading a selected project, writing a file, running a command, storing a design in Choro Design, or sending selected context to a provider you chose.
You grant Choro a limited, non-exclusive licence to host, copy, transmit, display, and technically process content placed in Choro Design only as needed to operate, secure, back up, and support that service. This licence ends when the content is deleted, except for limited backup or legal-retention copies described in the Privacy notice.
You are responsible for having the rights needed to use the content and systems you connect. Do not give an agent access to confidential material, production systems, or third-party data unless you are authorised to do so.
7. Acceptable use
You may not use Choro to violate law, infringe another person’s rights, bypass access controls, distribute malware, interfere with services, or gain unauthorised access to computers, accounts, repositories, or data. You may not misrepresent Choro as being endorsed by a third-party provider.
You may test Choro’s security in good faith under the reporting guidance on the Security page. Do not access other people’s data, degrade availability, or publicly disclose an unresolved vulnerability that could put users at risk.
8. Coding agents and terminal actions
Coding agents can generate incorrect code and may propose or execute commands that delete files, expose secrets, modify repositories, incur provider charges, or affect external systems. Choro’s interface does not make an agent’s output correct or safe.
You are responsible for reviewing plans, diffs, commands, permissions, and external side effects. Keep backups and version control, use least-privilege credentials, and use additional care before granting access to production environments.
9. Fees
Choro does not currently include a Choro-hosted paid plan or resell model usage. Third-party providers may charge you under their own plans, and you are responsible for those charges. If Choro later offers paid features, pricing and any additional payment terms will be presented before purchase.
10. Availability, changes, and ending access
Features may be changed, suspended, or removed. Builds may contain defects, and compatibility with macOS, third-party CLIs, provider interfaces, or local services can change. You may stop using Choro at any time by removing the application and its local data. Removing the desktop application does not by itself delete content already stored in Choro Design; contact privacy@choro.dev to request deletion.
Access to Choro-operated services may be restricted or withdrawn for misuse, security risk, or violation of these terms. Ending service access does not remove rights already granted under an applicable open-source licence.
11. Disclaimers and responsibility
To the fullest extent permitted by applicable law, Choro is provided “as is” and “as available”, without warranties of uninterrupted operation, fitness for a particular purpose, non-infringement, or error-free agent output.
To the fullest extent permitted by law, Choro’s operator and contributors will not be liable for indirect, incidental, special, consequential, or exemplary loss arising from use, including loss of data, code, revenue, credentials, or access to third-party services. Nothing in these terms excludes liability that cannot legally be excluded or limits mandatory consumer rights.
12. Changes and contact
These terms may change as Choro evolves. Material changes will be dated on this page and, where practical, communicated with the build, download flow, or release notes. Changes do not retroactively reduce rights already granted under an open-source licence.
Contact legal@choro.dev. Mandatory law in your place of residence continues to apply where it cannot be excluded by contract.