OpenCode
Run topencode and OpenCode launches with Together GLM 5.2 wired in - config injected only for that launch. Close it and your OpenCode setup is exactly as it was, while sessions can still resume.

Install once, then run GLM 5.2 in Claude Code or Codex with short commands. TogetherLink injects Together settings for that run only, so your normal tool configs stay clean.
topencodetclaudetcodextpicurl -fsSL https://togetherlink.vercel.app/ install.sh | shRun topencode and OpenCode launches with Together GLM 5.2 wired in - config injected only for that launch. Close it and your OpenCode setup is exactly as it was, while sessions can still resume.
Run tclaude and Claude Code routes through a local translation proxy - no edits to your real config. You keep your Claude Code subscription and login the whole time.
Run tcodex and Codex talks to Together through a local Responses-to-chat proxy. Settings are injected per run, with headless exec support for fast checks.
Run tpi and Pi Code launches with Pi's official Together provider, a temporary Pi config directory, and normal local session persistence.
Also works with the ChatGPT desktop app. Unlike the per-run CLI wrappers above, this persistently patches ChatGPT Desktop config so the app talks to Together. When you want your OpenAI subscription back, run the restore command.
Patches ChatGPT Desktop config to route through Together. The change stays active until you restore.
Brings back your OpenAI / ChatGPT subscription profile and removes the togetherlink config.
~/.togetherlink/backup/codex-app/.curl -fsSL https://togetherlink.vercel.app/ install.sh | sh~/.togetherlink/bin/ and adds togetherlink, tclaude, topencode, tcodex, and tpi.topencode, tclaude, or tcodex, or tpi. For the ChatGPT desktop app run togetherlink chatgpt (alpha), and restore it with togetherlink chatgpt --restore. On first launch it asks once for your Together API key - press Enter to skip and add it later.Prefer explicit commands? Use the long form instead of the short wrappers.