Ofox Desktop setup: connect your AI tools and agents
Set up Ofox Desktop on an Apple Silicon Mac, find supported coding tools, connect your account and check a first request before adding more clients.
Ofox 
Ofox Desktop helps you connect supported AI tools and agents to your Ofox account from one desktop app. Install Desktop on a compatible Mac, connect your account, choose an installed client and a suitable model, then check a small request before connecting your other tools.
This guide is for developers who use more than one coding tool and want a clearer way to manage their Ofox connections. The coding work still happens in the client you choose; Desktop handles the connection setup described on the official product page.
Scope: this is a documentation-based setup guide, checked on September 18, 2026. It is not a hands-on test of all six tools or a model-compatibility benchmark.
Which tools can you connect?
The current Desktop page names six supported tools. Start with one you already use, rather than installing every client to follow this guide.
| Tool listed by Desktop | Where to continue if you need client-specific help |
|---|---|
| Claude Code | Claude Code integration guide |
| Codex | Codex integration guide; check whether your installation is the CLI or desktop app |
| Gemini CLI | Gemini CLI integration guide |
| OpenCode | OpenCode integration guide |
| OpenClaw | OpenClaw integration guide |
| Hermes | Start with Desktop’s detected-client entry; use the integration index to find currently available documentation |
A tool appearing in the supported list does not establish that every version, model or tool-calling feature works with it. In particular, do not treat a reference to Codex as proof that the CLI and desktop app share the same configuration procedure.
Before installing Ofox Desktop
At the time of this check, the download page offers Ofox Desktop 1.3.2 for Apple Silicon Macs running macOS 12 or later. It does not offer Windows or Intel Mac installers. Use that page for the current download rather than bookmarking a versioned installer URL.
Have your preferred coding client installed and an Ofox account ready. The Desktop download is free; model requests are billed separately. Review the selected model’s current terms and your account balance before sending requests.
For your first connection, use an empty test folder instead of a business repository. Note any existing provider configuration you depend on. The product page describes automatic configuration backups and per-tool API keys; before changing another configuration, check that you can locate the backup described by Desktop.
Set up your first tool
1. Download and open Desktop
Download the installer from the official Desktop page, install the app and open it. If Desktop is already installed, start with that installation and check its version. You do not need to reinstall simply to connect another supported client.
2. Connect your Ofox account
Follow the account connection flow shown in the app. If you do not have an account, create an Ofox account first. When you check usage later, make sure you are signed in to the same Ofox account.
Connecting an account and completing a model request are separate milestones. A successful login alone does not demonstrate that a coding client is using the intended connection.
3. Select one detected client and a model
Choose the client you installed, select a model appropriate for that client and apply the configuration. Start with one connection so that any failure has fewer possible causes. The product page describes automatic discovery; if your tool is missing, check its installation and the corresponding integration guide before changing unrelated settings.
Do not choose a model solely because its name appears in a list. Your intended task may require tool calling or other capabilities in addition to text generation. Keep the model selection stable while checking the first connection.
4. Send a short request from the coding client
Open a fresh session in the selected client, using your test folder. Try this prompt:
Reply with exactly: OFOX_CONNECTION_CHECK.
Do not read files, run commands, or use tools.The expected text is OFOX_CONNECTION_CHECK. That is a test target, not an output captured for this article. Record the approximate request time and the selected model. If the request fails, save the error and investigate before repeatedly submitting it.
5. Match the response to your Ofox usage
Open your Ofox dashboard and find the corresponding request. Compare its time and model, and use the client-specific key information where available to distinguish it from other activity. Check the request status and the recorded charge.
A reply by itself is not enough: an existing session or configuration may still use a different provider. Likewise, a request record with no usable response is not a completed test. If you cannot identify the matching request, leave the connection unverified and check the client’s active settings.
Add the next tool without losing track
Once you can identify a successful request from the first client, repeat the process for your second client. For example, someone already using Claude Code and OpenCode can connect and check each separately.
Keep a small record as you go:
| Client and version | Selected model | Test time | Matching Ofox record | Result |
|---|---|---|---|---|
| Your first client | Fill in after selection | Fill in after sending | Found / not found | Verified / investigate |
| Your second client | Fill in after selection | Fill in after sending | Found / not found | Verified / investigate |
The first short request checks text connectivity. Before relying on a connection for development, test a small, non-sensitive coding task with a clear acceptance condition. Verify any file changes or tool execution separately. Successful text generation is not evidence that the full coding workflow has passed.
What to check when setup does not work
| What you see | What to check next |
|---|---|
| The client is not detected | Confirm it is installed and listed as supported; follow that client’s integration documentation |
| Authentication fails | Check the connected account and active client configuration; do not post API keys in support messages |
| The selected model cannot be used | Check the precise model selection, account access and the capabilities required by the client |
| A response arrives but no matching Ofox request appears | Check the dashboard account, request time and active provider configuration before declaring success |
| Text works but a coding task fails | Inspect the task error and required capabilities; do not treat text connectivity as a tool-calling test |
| You need the previous setup back | Use the configuration backup and restore workflow described for Desktop, then verify the restored client configuration |
For client-specific configuration details, use the linked technical documentation rather than combining instructions from different clients. If you seek support, include the tool version, selected model, time and a redacted error message.
Start with the tools you already use
Download Ofox Desktop, connect one supported client and check its first request. Then add the other tools you actually use, keeping a separate verification record for each. This gives you a manageable setup sequence without assuming that one successful connection validates every client.
Frequently Asked Questions
- Which tools does Ofox Desktop support?
- The official Desktop page lists Claude Code, Codex, Gemini CLI, OpenCode, OpenClaw and Hermes. Check the detected client and its version before applying a configuration.
- Does downloading Desktop include free API usage?
- No. The desktop download is free, while model requests use your Ofox account and are billed separately at the applicable model rates.
- Can I install this version on Windows or an Intel Mac?
- The download page checked for this guide offers an Apple Silicon installer for macOS 12 or later. It does not currently provide a Windows or Intel Mac installer.
