Cordy Documentation
Guides for Cordy Gateway, Chrome, Desktop, and Mobile, with source and release status for each product.
This site brings together the documentation for four separate Cordy projects. Each product has its own runtime, storage, provider support, and release process.
Choose a product
| Product | Purpose | Documentation baseline, checked 2026-09-13 |
|---|---|---|
| Cordy Gateway | Self-hosted model gateway with routing, API keys, member access, billing, and observability. | Tag 1.2.4 plus current main; no GitHub Release published. |
| Cordy for Chrome | Browser assistant for chat, page context, translation, and library workflows. | Source/tag 2.4.5; latest published GitHub Release 2.4.4. |
| Cordy Desktop | Workspace and terminal workbench for external CLI coding agents. | Source/tag 0.4.0; its Release is a draft, latest published Release 0.3.0. |
| Cordy for Mobile | Android-first BYOK chat with local conversations and supported image/voice input. | Release 0.5.0 plus current main changes; iOS execution remains unverified. |
A source tag or changelog entry does not establish installer availability. Follow each product's installation page for the checked distribution path. The source repositories currently require repository access.
Start here
- Gateway setup: run the service and configure access to upstream models.
- Chrome installation: load the extension and choose a provider.
- Desktop installation: install the available build or run from source, then launch your CLI agent.
- Mobile setup: build/install Android and configure your provider.
Shared concepts, product-specific limits
BYOK means you choose credentials and providers; it does not mean every model runs on your device. Privacy and storage differ between browser storage, the desktop runtime, mobile secure storage, and a deployed gateway. Check the provider matrix before connecting clients: protocol compatibility alone does not guarantee every model feature or modality.
The changelogs mirror upstream source history, including unreleased work where recorded. Product guides distinguish that history from published releases and platform verification.