Skip to content

Features

Common workflows for connections, MCP, skills, sessions, usage, remote nodes, and appearance.

Updated View as Markdown
For humans

After the first connection works, choose a guide by task. Most settings take effect immediately. Pages call out actions that overwrite data or rewrite live tool configuration.

I want to… Start here
Switch connections on WSL or a development machine Control remote nodes over SSH
Change the API used by one app Manage connections
Give several apps the same MCP server or skill MCP and skills
Find a conversation, token count, or request cost Sessions and usage
Change language, startup behavior, or visible apps Settings and themes
Configure authentication or fields unique to one CLI Choose an app-specific guide below

Remote nodes

Control ochcli on WSL, development machines, and headless servers over SSH.

Read the guide

Manage connections

Discover, edit, order, copy, and switch direct connections for each app.

Read the guide

MCP and skills

Store shared capabilities once, then enable and sync them per supported app.

Read the guide

Sessions and usage

Browse local conversations and understand tokens, cache, cost, and request details.

Read the guide

Settings and themes

Adjust language, startup behavior, app visibility, terminals, and themes.

Read the guide

Configure a specific tool

The connection workflow is shared, but write modes, authentication, and advanced capabilities differ. Each tool has its own guide group:

Tool Guide Write mode MCP Skills
Claude Code Configure Claude Current-connection switching Yes Yes
Claude Desktop Configure Claude Current-connection switching No No
Codex Configure Codex Current-connection switching Yes Yes
Cherry Studio Import into Cherry Studio Confirmed Deep Link import No No
Grok Build Configure Grok Build Current-connection switching Yes No
Kimi Code Configure Kimi Code Current-connection switching No No
OpenCode Configure OpenCode Multiple connections coexist Yes Yes
OpenClaw Configure OpenClaw Multiple connections coexist No No
Hermes Configure Hermes Multiple connections coexist Yes Yes

In current-connection switching, the tool’s live configuration points to one active connection. In coexistence mode, OcHub writes several connections into one tool configuration, and Remove from tool deletes only that entry. Cherry Studio is import-only and confirms every handoff in its own window.

When moving existing data from cc-switch, start with the migration guide for ID-collision, backup, and staged verification guidance.

For model routing, database restoration, or app-specific JSON, continue to Advanced features.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close