Agent CLI.
Use an installed coding agent and its existing provider login.
Verified for Gyro 0.1.0-alpha.49.7Choose an integration
Gyro uses the provider’s CLI on your Mac. Install it and complete its login before connecting. Subscription eligibility, authentication, and usage charges are set by the provider.
| Integration | Gyro status | Official setup |
|---|---|---|
| Claude Code | Supported | Installation & login for Claude Code↗ |
| Codex | Supported | Installation & login for Codex↗ |
| Gemini CLI | Supported | Installation & login for Gemini CLI↗ |
| Kimi Code | Supported | Installation & login for Kimi Code↗ |
| Grok Build | Supported | Installation & login for Grok Build↗ |
| Cursor | Experimental | Installation & login for Cursor↗ |
| OpenCode | Experimental | Installation & login for OpenCode↗ |
Cursor and OpenCode are experimental in this release. Features and session behavior may differ from the supported integrations.
Install and sign in
- Follow the official setup link for your chosen CLI. Check its own macOS and runtime requirements.
- Open your terminal and confirm that the CLI starts. Complete the provider’s authentication flow and verify that it can run a task.
- Finish installation and login before opening Gyro, or quit and reopen Gyro afterward so it can detect the CLI.
A cloud-backed CLI sends task context to its provider. A subscription does not necessarily include all models or usage. Provider processing details.
Connect in Gyro
- Open Gyro’s Settings → Providers. Enable your installed agent CLI.
- Return to your project session and choose that provider in the chat picker.
- Start the small first task. Review requested tool approvals.
Connected: the selected provider starts and returns a response in your project session.
If it does not start
Check that the same CLI works and is signed in in your terminal. Reopen Gyro after installing or changing the executable. For login failures or an unavailable CLI, follow CLI troubleshooting.
Do not paste provider tokens into a chat or support report. Gyro uses the CLI’s login; its saved model API keys are a separate connection path.