Choose a technical integration
Clovis can be used from a desktop application, a terminal, a code editor, or an automation tool. Start by choosing the interface in which you want to work.
Recommendation for development
For the recommended integration, use OpenCode CLI directly from the terminal. If you prefer a fully graphical setup, use OpenCode Desktop.
Quick comparison
| Integration | Primary use | Interface | Choose it if… |
|---|---|---|---|
| OpenCode CLI — recommended | Development assistance | Terminal | you want to work on a project from the terminal, regardless of your editor |
| OpenCode Desktop | Development assistance | Desktop application | you want to configure Clovis graphically and switch easily between Git projects |
| Cline | Development assistance | VS Code extension | you want to stay in VS Code with a straightforward setup |
| RooCode | Development assistance | VS Code extension | your team already uses RooCode or wants to standardize on this extension |
| n8n | Workflow automation | n8n interface | you want to connect Clovis to a workflow, an agent, or business tools without building the entire orchestration in code |
How to choose
- Looking for the recommended development integration? Use OpenCode CLI.
- Prefer a standalone graphical interface? Use OpenCode Desktop.
- Want to stay in VS Code? Use Cline or RooCode.
- Building an automated workflow rather than a software project? Use n8n.
All these integrations use a Clovis API key. Create a dedicated key for each integration in the Clovis administration console so that you can monitor its usage and revoke it independently.
Protect API keys
An API key is a secret. Never add it to a Git repository, a shared file, or a screenshot.