This table focuses on connecting each tool through the Nbility custom gateway. Features and interfaces change between client releases; use each tool's official documentation and its linked setup guide as the final reference.
Quick comparison
| Tool | Main surface | Nbility setup | Best for | Important boundary |
|---|---|---|---|---|
| Claude Code | CLI, IDE integration | Anthropic environment variables | Native Claude tooling | Base URL omits /v1 |
| Codex | CLI, IDE extension, desktop | Custom Responses provider in config.toml | GPT/Codex workflows | Only the Responses wire API is supported |
| Roo Code | VS Code/Cursor extension | OpenAI Compatible profile | Arbitrary compatible gateways in an editor | Model must support native tool calling |
| OpenCode | TUI, desktop, IDE | /connect + opencode.json | Multiple providers and reviewable config | Chat Completions and Responses use different adapters |
| Qwen Code | CLI | modelProviders + environment variable | CLI model switching | Legacy security.auth.* credential fields are deprecated |
| Droid CLI | CLI, IDE integration | BYOK in settings.json | Factory workflows and custom models | Provider type must match the protocol |
| OpenClaw | Gateway, web/channel clients | models.providers | Persistent agents and fallback chains | Capability metadata is declared manually |
| DeepSeek Harness | Web UI, headless | Custom OpenAI-compatible provider | Plugin-based agent harness experiments | Still in developer preview |
| ZCF | Configuration tool | Interactive Claude Code/Codex generation | One-stop workflow setup | Edits multiple client configuration files |
| Cursor | Editor | Conditional Base URL override | Existing Cursor users | Official docs do not guarantee full arbitrary-gateway BYOK |
Choose by workflow
- Smallest setup: Claude Code or Roo Code.
- OpenAI Responses/Codex workflow: Codex.
- Multiple terminal providers: OpenCode or Qwen Code.
- Explicit OpenAI Compatible support inside VS Code: Roo Code.
- Persistent Gateway, channels, and fallback chains: OpenClaw.
- Install workflows, MCP, and profile switching together: ZCF.
- Experiment with a new plugin-based agent harness: DeepSeek Harness.
Cursor has more custom-gateway boundaries and is not ideal for the first Nbility verification. Test the key with API Quickstart or a client with explicit custom-provider support first.
Protocols and Base URLs
| Client configuration | Base URL | Protocol |
|---|---|---|
| OpenAI Chat/Responses | https://api.nbility.ai/v1 | /chat/completions or /responses |
| Anthropic Messages | https://api.nbility.ai | Client appends /v1/messages |
| Native Gemini | https://api.nbility.ai | Client appends /v1beta/models/... |
A protocol mismatch commonly causes 404, empty output, or failed tools. API compatibility does not mean every model supports images, tools, realtime audio, or structured output.