togetherlink
Claude Code compatibility guide · 10 min

Connect Claude Code to GLM 5.2, Kimi, and DeepSeek

Keep the Claude Code terminal experience and route model calls to GLM 5.2, Kimi, DeepSeek, or another curated Together model—without replacing your Claude settings.

By TogetherLink

TLtogetherlinkNAMED-MODEL COMPATIBILITYConnect Claude Code toGLM 5.2, Kimi + DeepSeek$tclaudeGLM 5.2 + more · Messages APIClaude CodePOWERED BY

The short answer

TogetherLink starts a local compatibility proxy for Claude Code. It forwards model requests to Together AI and streams responses back in the format Claude Code expects.

Before you start

Two tools and one required key

01

Claude Code

Install it and complete Claude's normal sign-in once.

02

TogetherLink

Install the local routing binary with the command below.

03

Together key

Create a Together API key and make sure the account has available credit.

New to Claude Code? Follow Anthropic's official setup guide, then sign in once before launching tclaude.

Install TogetherLink
$curl -fsSL https://togetherlink.vercel.app/install.sh | bash
Save the Together API key
$togetherlink configure
Launch Claude Code on Kimi K3
$tclaude
Pin GLM 5.2 for a scripted run
$togetherlink --model zai-org/GLM-5.2 claude -p "task"

The installer also adds tcodex, tchatgpt, tgrok, thermes, tpi, tprime, tdeepseek, and topencode. Use the full togetherlink claude command in scripts when you want the target tool to be explicit. Put --model before the harness name so TogetherLink consumes it instead of passing it to Claude Code.

What changes for the launched process
AreaTogetherLink runNormal Claude Code
Model endpointLocal Anthropic-compatible proxyAnthropic
Model billingTogether API accountYour Anthropic plan
Claude loginPreservedPreserved
Saved settingsNot rewrittenUsed normally
File and shell toolsRun by Claude CodeRun by Claude Code
Live proof

Claude Code reading a sample repository

This non-interactive run asked Claude Code to inspect a TypeScript file without editing it. The TogetherLink banner shows that Claude Code was configured to use GLM 5.2 on Together AI rather than Anthropic.

Real Warp terminal running TogetherLink with Claude Code and GLM 5.2 in a TypeScript sample repository
A real Warp window captured after a headless TogetherLink v0.6.4 Claude Code run on July 20, 2026. No terminal output was recreated or edited.

Web search is a separate, optional key

Claude Code's model calls use Together. If a Claude workflow invokes web search, TogetherLink can emulate that tool with Exa. Add an Exa key during togetherlink configure only when you want that feature; it is not required for repository work, shell commands, or file edits.

Verify the provider before trusting the result

At startup, read the line printed before Claude Code opens. With the default model, it should say:

togetherlink ▸ Routing Claude Code → Together AI (Kimi K3). Not Anthropic.

If you do not see that line, stop and check that you launched togetherlink claude or tclaude, not plain claude.

Optional model choice

Switch models after the first Claude run

Start with tclaude. For an override, TogetherLink options go before claude, while Claude Code arguments go after it.

Interactive session on DeepSeek V4 Pro
$togetherlink --model deepseek-ai/DeepSeek-V4-Pro-0813 claude
One-shot GLM 5.2 prompt
$togetherlink --model zai-org/GLM-5.2 claude -p "Summarize the current diff"
Kimi K3
moonshotai/Kimi-K3

Default · vision · reasoning · 1M context

GLM 5.2
zai-org/GLM-5.2

text · reasoning · 512K context

DeepSeek V4 Pro 0813
deepseek-ai/DeepSeek-V4-Pro-0813

text · reasoning · 1M context

Qwen 3.7 Max
Qwen/Qwen3.7-Max

vision · reasoning · 1M context

DeepSeek V4 Flash 0731
deepseek-ai/DeepSeek-V4-Flash-0731

text · reasoning · 1M context

Correcttogetherlink --model MODEL claude -p "..."
Wrong ordertogetherlink claude --model MODEL
Common questions

FAQ

Can Claude Code run Together AI models?+

Yes. TogetherLink launches Claude Code against a local Anthropic Messages-compatible proxy, then sends each request to the selected Together AI model.

Do I still need Claude Code installed?+

Yes. TogetherLink is a routing layer, not a replacement interface. Install and sign in to Claude Code normally, then launch it through togetherlink or the tclaude shortcut.

Will TogetherLink log me out of Claude Code?+

No. The Together provider is injected only for the launched process. Your Claude Code login and normal settings remain available when you launch Claude Code normally.

Why do I need a Together API key if I pay for Claude?+

Your Claude plan covers Claude usage provided through Anthropic; it does not pay for model calls made through Together AI. Together requires its own API key and bills those model tokens separately.

Do I need an Exa API key?+

Only if you want TogetherLink's Claude web-search emulation. The Together key covers model requests, while Claude Code runs file and shell tools locally. Neither requires an Exa key.

How do I change the Together model used by Claude Code?+

Place --model and the exact Together model ID before claude. For example: togetherlink --model deepseek-ai/DeepSeek-V4-Pro-0813 claude.

Can I use Claude Code's non-interactive -p mode?+

Yes. Arguments after claude go to Claude Code, so togetherlink --model zai-org/GLM-5.2 claude -p followed by a prompt uses the same local proxy.

Compare with Codex