Other clients
Stravia supports nine additional CLI tools. Use Connect clients to preview configuration or apply it (Desktop only); all clients accept Stravia as a provider alongside others.
Prerequisites
Connect an upstream Model Service, create an enabled Stravia Model ID with an enabled destination, and create an enabled API Key authorized for that model. Check the selected client supports the protocol shown in its row before applying configuration.
Supported clients and protocols
| Client | Protocol | Configuration |
|---|---|---|
| OpenCode | open-responses | See OpenCode |
| OpenClaw | openai-compatible | ~/.openclaw/openclaw.json |
| Hermes Agent | openai-compatible | ~/.hermes/config.yaml + ~/.hermes/.env |
| TRAE | openai-compatible | ~/.config/trae/trae_config.yaml |
| WorkBuddy | openai-compatible | ~/.workbuddy/models.json |
| ZCode | openai-compatible | ~/.zcode/v2/config.json |
| DeepSeek Harness | openai-compatible | ~/.dsh/settings.yaml + ~/.dsh/.credentials.yaml (or $DSH_HOME) |
| Pi | open-responses | ~/.pi/agent/models.json (or $PI_CODING_AGENT_DIR) |
| OMP | open-responses | ~/.omp/agent/models.yml |
Configure using Stravia Connect
- Go to Connect clients and select the desired client.
- Choose your API Key and authorized models.
- Preview the configuration or Apply to Client (Desktop only).
- For web-based Server, copy the preview and apply it manually to your client.
Per-client configuration
Each client has different configuration requirements. When using Connect clients:
- Click Preview to see the exact configuration for your selected client.
- For Desktop, click Apply to Client to write directly to the configuration file.
- For web-based Server, copy the preview content and apply it manually to your client's configuration file.
The preview includes all required fields and model metadata for your chosen client and selected models.
Verify the connection
After applying configuration, use the client to make a request. Check Request history in Stravia to confirm the request arrived and the model responded.
Troubleshoot a failed request
Confirm the client's endpoint and protocol match the table, its credential is the Stravia API Key, and its requested Model ID is enabled and allowed by that key. For clients with generated configuration, compare required fields and metadata with the Stravia Preview. If Request history has no interaction, check the endpoint and network path from the client; if an interaction exists, inspect its target and error. A successful preview or file write is not a successful client request.
Application-specific clients
WorkBuddy, ZCode, Pi, and OMP store configuration in application-specific locations or environment variables. Use the preview from Connect clients and consult your client's documentation for the exact configuration method.
Next steps
For SDK and code examples see SDK . For general client configuration see Connect clients .