Home Getting started Providers Reference Legal
Home / Legal & notices

Legal & notices

Disclaimers, platform requirements, open-source credits, and licensing information for Claude Dialects.

Disclaimer

Independent, unofficial project

Claude Dialects is an independent, unofficial project. It is not affiliated with or endorsed by Anthropic, OpenAI, Google, Moonshot AI, Z.ai, xAI, Cursor, GitHub, Microsoft, MiniMax, DeepSeek, or the CLIProxyAPI maintainers.

Product and company names mentioned on this site and in the documentation are trademarks of their respective owners. References to third-party products, services, or APIs do not imply sponsorship, partnership, or approval.

Your responsibility: You are solely responsible for complying with each provider's terms of service, subscription rules, usage policies, and applicable laws when using Claude Dialects. The authors and contributors of this project cannot be held liable for how you configure dialects, which models you access, or how you use generated commands in your environment.

Claude Dialects wraps the real Claude Code application and routes requests through provider-specific proxies or SDK bridges. It does not replace provider billing, authentication requirements, or account eligibility checks imposed by upstream services.

Platform requirements

macOS only

The current target platform is macOS. Linux and Windows builds are not supported at this time. Do not expect this project to run correctly on other platforms without additional porting work.

Additional requirements:

  • Go 1.26.5 or newer — build the cc-dialect executable from source
  • Claude Code available as claude on your PATH
  • Node.js 22.13+ and npm (optional) — only for Cursor and GitHub Copilot SDK dialects
  • Node.js 22.13.x or 24+ and npm — contributor requirement when rebuilding or verifying dashboard source

The dashboard frontend is compiled, committed, and embedded in the Go executable. It does not download frontend assets at runtime, and Node.js is not required to run it or for a normal make build or make install from a clean checkout.

This project does not publish prebuilt binaries or GitHub releases. Everyone builds the executable from the checked-out source. Locally produced archives from make assets are not signed or notarized by this project.

Open-source components

Claude Dialects embeds or installs several third-party components. Each remains under its own license and terms.

CLIProxyAPI

Embedded via Go SDK · MIT License

The heart of proxied dialects. CLIProxyAPI translates Claude Code's Anthropic-compatible API calls to upstream providers (OpenAI Codex, Kimi, Gemini via Antigravity, xAI, Anthropic OAuth, and custom Anthropic-compatible endpoints). It is linked directly into the cc-dialect executable — there is no separate proxy download, container, or global installation step.

CLIProxyAPI is pinned as a Go dependency so a new upstream release cannot alter an already-built executable. Its MIT license permits embedding and redistribution.

@cursor/sdk

Installed on demand · Cursor license & terms

Cursor dialects use a local OpenAI-compatible bridge backed by the official Cursor SDK. The SDK is installed on demand via cc-dialect cursor install rather than bundled in this repository. It remains a separately licensed Cursor dependency; usage is billed through your Cursor API key.

@github/copilot-sdk

Installed on demand · GitHub license & terms

GitHub Copilot dialects use the official Copilot SDK and its bundled CLI runtime. Install via cc-dialect copilot install. Copilot prompts consume your account's normal Copilot usage allowance and are subject to GitHub's policies.

Embedded dashboard frontend

Bundled web assets · third-party npm licenses

The localhost dashboard is built from React, React Router, Radix UI components, Lucide React, and supporting frontend libraries. Production dependencies are compiled into internal/app/dashboard/dist/ and embedded in the cc-dialect binary. Their license notices are included in THIRD_PARTY_NOTICES.md. Build and test tools such as Vite, TypeScript, Vitest, Tailwind CSS, jsdom, and Testing Library are contributor dependencies and are not shipped as runtime Node packages.

Claude Code

External dependency · Anthropic terms

Every dialect launches the real Claude Code binary. Claude Code itself is subject to Anthropic's terms and requires a valid installation on your system. Claude Dialects does not redistribute Claude Code.

Third-party notices

Licenses and notices for Go modules compiled into the cc-dialect binary and production npm dependencies bundled into its embedded dashboard are included in the repository's THIRD_PARTY_NOTICES.md file. This committed file is regenerated after dependency updates; development-only frontend packages are not included.

When you install Cursor or Copilot SDK dialects, additional third-party packages are downloaded into cursor-runtime/ and copilot-runtime/ under your dialect home directory. Those packages carry their own licenses as declared by their publishers.

No warranty

This software is provided "as is", without warranty of any kind, express or implied. See the MIT License for the full disclaimer of liability.

License

Claude Dialects is available under the MIT License.

Copyright © 2026 Stefan de Vogelaere

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files, 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, subject to the conditions in the license text.

Security reporting

Report vulnerabilities privately through GitHub Security Advisories, not through public issues. See SECURITY.md in the repository for the full policy.

Proxy servers and SDK bridges bind only to 127.0.0.1. The web dashboard accepts numeric loopback listeners only, requires the exact bound Host on every request, and requires the exact Origin plus a per-process CSRF token for state changes. Its API omits credential contents, keys, token values, and other private fields.

The dashboard has no separate user login and assumes one trusted local user. These browser controls do not stop another process running as that user from connecting to loopback and obtaining the CSRF token. Remote access, port forwarding, and reverse-proxy exposure are unsupported. Securing the local machine and provider accounts remains your responsibility.