Skip to content

Overview

What OcHub is, what it manages, and how it relates to your existing tool configuration.

Updated View as Markdown

OcHub is a native desktop control center for AI coding tools. It lets you switch model providers, manage shared capabilities, and run a local gateway from one place — without a browser shell or webview.

A useful mental model

Think of OcHub as three layers:

  1. Apps are the tools you actually run, such as Claude Code or Codex.
  2. Connections describe how one app authenticates and reaches an API.
  3. Model providers are optional shared upstreams behind OcHub’s local gateway.

Start with an app and a direct connection. Add the gateway layer only when you need shared routing, interface conversion, or fallback.

What OcHub manages

OcHub manages Claude Code, Claude Desktop, Codex, Cherry Studio, Grok Build, Kimi Code, OpenCode, OpenClaw, and Hermes.

Area Capabilities
Connections Discover, import, edit, switch, and test direct API connections
Model providers Route supported clients through a local gateway with model aliases, reasoning mapping, interface-candidate retry, backup-provider switching, health checks, and usage accounting
Shared tools Manage MCP servers and reusable skills across supported clients
Remote nodes Switch existing connections and operate Gateway on WSL, development machines, and headless servers over SSH
Operations Browse sessions, inspect usage, configure sync, and manage app behavior
Migration One-time, read-only import from compatible cc-switch databases

How it touches your configuration

OcHub owns ~/.ochub/ and never writes back to ~/.cc-switch/. It does update the live configuration directories of tools you explicitly manage.

Where to go next

Navigation

Type to search…

↑↓ navigate↵ selectEsc close