Gemini, Cursor, Copilot, Kimi, Hermes
Beyond Claude Code, Codex, and OpenCode, Vicoa now supports more coding agents that you launch directly from a new session — no extra vicoa <agent> command needed:
- Gemini — Google's Gemini CLI
- Cursor — Cursor CLI
- Copilot — GitHub Copilot CLI
- Kimi — Kimi CLI
- Hermes — Nous Research's Hermes
These agents are integrated through the Agent Client Protocol (ACP) and run on your own machine using your own credentials. Vicoa never stores your provider keys.
1. Update Vicoa to the latest version
Support for these agents requires Vicoa CLI v1.6.1 or later and the mobile app v1.6.8 or later. Upgrade the CLI with:
npm i -g @vicoa/cli@latestCheck your version:
vicoa --version
# It should be at least v1.6.1Update the mobile app from the App Store (iOS) or Google Play (Android).
See Version Compatibility for the full matrix.
2. Install the agent and start the daemon
Each agent runs from its own CLI on the machine. Install the agent's CLI there and sign in with your own account.
| Agent | CLI to install |
|---|---|
| Gemini | Gemini CLI |
| Cursor | Cursor CLI |
| Copilot | GitHub Copilot CLI |
| Kimi | Kimi CLI |
| Hermes | Hermes Agent |
Start the Vicoa daemon on the machine:
vicoa daemon3. Start a new session
Instead of a dedicated command, start these agents straight from New Session in the web dashboard or mobile app: pick the machine, choose the agent, pick a model, and go.
From the web
From your phone
Choosing a model
The first time you start a session with an agent on a machine, the new-session picker offers a set of default preset models.
Once that agent has run on the machine at least once, Vicoa fetches the models actually available for it there, and shows that available models on the machine afterward.
You can also change your model from under the same coding agent during a session.
Troubleshooting
- Shows "Not Installed" for an agent you've installed? Vicoa detects installed agents when the daemon starts. If you installed the agent's CLI after starting Vicoa, run
vicoa daemonagain so it picks up the newly installed agent. - New agents don't appear? They only show when both the CLI (≥ v1.6.1) and the app (≥ v1.6.8) are up to date. See Version Compatibility.