second-state · alabulei1 · Jul 14, 2026 · Jul 14, 2026
diff --git a/src/content/writings/en/gpt-5-6-token-station.md b/src/content/writings/en/gpt-5-6-token-station.md
@@ -2,7 +2,7 @@
 slug: gpt-5-6-token-station
 lang: en
 title: "GPT-5.6 is now on Token Station: try it in your coding agent routes"
-summary: "Token Station now supports GPT-5.6 across OpenAI-compatible API and coding-agent routes, including Codex and Copilot surfaces. Use one endpoint to compare Sol, Terra, Luna, and Claude Fable 5 in real workflows."
+summary: "Token Station now supports GPT-5.6 across the OpenAI-compatible API and Codex-style coding-agent routes. Use one endpoint to compare Sol, Terra, Luna, and Claude Fable 5 in real workflows."
 category: product
 date: 2026-07-13
 cta: https://models.bytefuture.ai/intro.html
@@ -11,7 +11,7 @@ cover: blog/gpt-5-6-token-station-cover.png
 
 GPT-5.6 is now available on Token Station.
 
-For coding-agent teams, what matters is that GPT-5.6 can be tested through the routes developers already use: a direct OpenAI-compatible API, OpenAI Codex-style workflows, and GitHub Copilot routes where the supported catalog exposes the model.
+For coding-agent teams, what matters is that GPT-5.6 can be tested through the routes developers already use: a direct OpenAI-compatible API and OpenAI Codex-style workflows.
 
 That turns GPT-5.6 from a launch announcement into something you can actually route, compare, and adopt without rebuilding your agent stack.
 
@@ -24,12 +24,6 @@ Token Station exposes the GPT-5.6 family through direct OpenAI-compatible routes
 - `openai/gpt-5.6-terra`
 - `openai/gpt-5.6-luna`
 
-And GitHub Copilot routes where the supported catalog publishes availability:
-
-- `github-copilot/gpt-5.6-sol`
-- `github-copilot/gpt-5.6-terra`
-- `github-copilot/gpt-5.6-luna`
-
 OpenAI Codex-style workflows use these same `openai/` routes, so there is no separate Codex route to set up.
 
 The result is simple: you can test the same model family from the surface that matches your workflow instead of treating each provider interface as a separate integration project.
@@ -50,11 +44,11 @@ curl https://models.bytefuture.ai/v1/chat/completions \
   }'
 ```
 
-To try a Copilot route, use:
+To switch variants, change only the `model` field:
 
 ```json
 {
-  "model": "github-copilot/gpt-5.6-luna"
+  "model": "openai/gpt-5.6-terra"
 }
 ```
 
@@ -99,11 +93,11 @@ Above 272K input tokens, GPT-5.6 uses a long-context tier: Sol doubles input and
 
 Claude Fable 5 is still a natural comparison point for long-running coding agents. It is configured in Token Station with a 1M context window and a higher $10/$50 price profile.
 
-GPT-5.6 brings a different operating shape: OpenAI-native routes, Codex and Copilot surfaces, and multiple price tiers in the same family.
+GPT-5.6 brings a different operating shape: OpenAI-native routes, Codex-style surfaces, and multiple price tiers in the same family.
 
 A simple starting point:
 
-- Reach for the GPT-5.6 family when you want OpenAI-native routes, Codex or Copilot surfaces, or a cheaper tier for high-volume steps. Pick Sol, Terra, or Luna by task, as above.
+- Reach for the GPT-5.6 family when you want OpenAI-native routes, Codex-style surfaces, or a cheaper tier for high-volume steps. Pick Sol, Terra, or Luna by task, as above.
 - Reach for Claude Fable 5 when you specifically want Anthropic's long-running-agent behavior and its 1M context, and are willing to pay the higher rate.
 - Compare them inside Token Station when workflow fit matters more than model-brand loyalty.
 
@@ -119,7 +113,7 @@ GMI Cloud and AWS Bedrock OpenAI catalogs were not added because their public ca
 
 If you already use Token Station, GPT-5.6 is now another route family you can test in your coding-agent workflow.
 
-Start with the direct OpenAI route for a simple API check. Use the same `openai/` route in your Codex setup for terminal coding tasks. Try the Copilot route if your workflow depends on GitHub Copilot's supported model catalog.
+Start with the direct OpenAI route for a simple API check. Use the same `openai/` route in your Codex setup for terminal coding tasks.
 
 Token Station gives you one place to compare those routes without rewriting your agent stack for every model launch.
 

diff --git a/src/content/writings/ja/gpt-5-6-token-station.md b/src/content/writings/ja/gpt-5-6-token-station.md
@@ -2,7 +2,7 @@
 slug: gpt-5-6-token-station
 lang: ja
 title: "GPT-5.6 が Token Station に登場：coding agent のルートでそのまま試す"
-summary: "Token Station は GPT-5.6 を OpenAI-compatible API、Codex、Copilot などの coding-agent ルートでサポートしました。1 つの endpoint から Sol、Terra、Luna、Claude Fable 5 を実際の workflow で比較できます。"
+summary: "Token Station は GPT-5.6 を OpenAI-compatible API と Codex スタイルの coding-agent ルートでサポートしました。1 つの endpoint から Sol、Terra、Luna、Claude Fable 5 を実際の workflow で比較できます。"
 category: product
 date: 2026-07-13
 cta: https://models.bytefuture.ai/intro.html
@@ -11,7 +11,7 @@ cover: blog/gpt-5-6-token-station-cover.png
 
 GPT-5.6 が Token Station で使えるようになりました。
 
-coding-agent チームにとって重要なのは、GPT-5.6 を開発者がすでに使っているルートで試せることです。直接の OpenAI-compatible API、OpenAI Codex スタイルの workflow、そして対応 catalog が公開している GitHub Copilot ルートです。
+coding-agent チームにとって重要なのは、GPT-5.6 を開発者がすでに使っているルートで試せることです。直接の OpenAI-compatible API と OpenAI Codex スタイルの workflow です。
 
 つまり GPT-5.6 は単なる発表ではなく、agent stack を作り直さずに route して、比較して、採用を判断できる選択肢になります。
 
@@ -24,12 +24,6 @@ coding-agent チームにとって重要なのは、GPT-5.6 を開発者がす
 - `openai/gpt-5.6-terra`
 - `openai/gpt-5.6-luna`
 
-GitHub Copilot catalog で公開されているルート：
-
-- `github-copilot/gpt-5.6-sol`
-- `github-copilot/gpt-5.6-terra`
-- `github-copilot/gpt-5.6-luna`
-
 OpenAI Codex スタイルの workflow は上記と同じ `openai/` ルートを使うため、別途 Codex 専用ルートを設定する必要はありません。
 
 同じモデルファミリーを、自分の workflow に合う surface から試せます。
@@ -48,11 +42,11 @@ curl https://models.bytefuture.ai/v1/chat/completions \
   }'
 ```
 
-Copilot ルートなら：
+variant を切り替えるには `model` フィールドだけを変えます。
 
 ```json
 {
-  "model": "github-copilot/gpt-5.6-luna"
+  "model": "openai/gpt-5.6-terra"
 }
 ```
 
@@ -97,11 +91,11 @@ Token Station は GPT-5.6 の `cache_write_tokens` を cache-creation bucket に
 
 Claude Fable 5 は long-running coding agent の自然な比較対象です。Token Station では 1M context window と $10/$50 の高い price profile で設定されています。
 
-GPT-5.6 は別の運用形を持ちます。OpenAI-native route、Codex/Copilot surface、そして同じ family 内の複数 price tier です。
+GPT-5.6 は別の運用形を持ちます。OpenAI-native route、Codex スタイルの surface、そして同じ family 内の複数 price tier です。
 
 まずはこう選べます。
 
-- OpenAI-native route、Codex や Copilot surface、あるいは高頻度な step に安い tier が欲しいなら GPT-5.6 ファミリー。Sol、Terra、Luna は上記のとおりタスクごとに選ぶ。
+- OpenAI-native route、Codex スタイルの surface、あるいは高頻度な step に安い tier が欲しいなら GPT-5.6 ファミリー。Sol、Terra、Luna は上記のとおりタスクごとに選ぶ。
 - Anthropic の long-running-agent behavior と 1M context を重視し、高い価格を許容するなら Claude Fable 5。
 - workflow fit が model brand より重要なら Token Station 内で比較する。
 
@@ -117,6 +111,6 @@ GMI Cloud と AWS Bedrock OpenAI catalog は、公開 catalog に GPT-5.6 がな
 
 Token Station を使っているなら、GPT-5.6 は coding-agent workflow に追加できる新しい route family です。
 
-direct OpenAI route で API check を行い、Codex では同じ `openai/` ルートを設定して terminal coding task を試し、GitHub Copilot catalog に依存する workflow なら Copilot route を試せます。
+direct OpenAI route で API check を行い、Codex では同じ `openai/` ルートを設定して terminal coding task を試せます。
 
 [Token Station を試す](https://models.bytefuture.ai/intro.html)
diff --git a/src/content/writings/ko/gpt-5-6-token-station.md b/src/content/writings/ko/gpt-5-6-token-station.md
@@ -2,7 +2,7 @@
 slug: gpt-5-6-token-station
 lang: ko
 title: "GPT-5.6이 Token Station에 추가되었습니다: coding agent route에서 바로 테스트하기"
-summary: "Token Station은 GPT-5.6을 OpenAI-compatible API, Codex, Copilot 같은 coding-agent route에서 지원합니다. 하나의 endpoint로 Sol, Terra, Luna, Claude Fable 5를 실제 workflow에서 비교할 수 있습니다."
+summary: "Token Station은 GPT-5.6을 OpenAI-compatible API와 Codex 스타일 coding-agent route에서 지원합니다. 하나의 endpoint로 Sol, Terra, Luna, Claude Fable 5를 실제 workflow에서 비교할 수 있습니다."
 category: product
 date: 2026-07-13
 cta: https://models.bytefuture.ai/intro.html
@@ -11,7 +11,7 @@ cover: blog/gpt-5-6-token-station-cover.png
 
 GPT-5.6을 이제 Token Station에서 사용할 수 있습니다.
 
-coding-agent 팀에게 중요한 점은 GPT-5.6을 개발자가 이미 쓰는 route에서 테스트할 수 있다는 것입니다. 직접 OpenAI-compatible API, OpenAI Codex 스타일 workflow, 그리고 지원 catalog가 공개한 GitHub Copilot route입니다.
+coding-agent 팀에게 중요한 점은 GPT-5.6을 개발자가 이미 쓰는 route에서 테스트할 수 있다는 것입니다. 직접 OpenAI-compatible API와 OpenAI Codex 스타일 workflow입니다.
 
 즉 GPT-5.6은 단순한 출시 소식이 아니라, agent stack을 다시 만들지 않고 route하고 비교하고 도입을 판단할 수 있는 선택지가 됩니다.
 
@@ -24,12 +24,6 @@ coding-agent 팀에게 중요한 점은 GPT-5.6을 개발자가 이미 쓰는 ro
 - `openai/gpt-5.6-terra`
 - `openai/gpt-5.6-luna`
 
-GitHub Copilot catalog가 공개한 route:
-
-- `github-copilot/gpt-5.6-sol`
-- `github-copilot/gpt-5.6-terra`
-- `github-copilot/gpt-5.6-luna`
-
 OpenAI Codex 스타일 workflow는 위의 `openai/` route를 그대로 사용하므로, 별도의 Codex route를 설정할 필요가 없습니다.
 
 같은 모델 패밀리를 workflow에 맞는 surface에서 테스트할 수 있습니다.
@@ -48,11 +42,11 @@ curl https://models.bytefuture.ai/v1/chat/completions \
   }'
 ```
 
-Copilot route는 다음처럼 사용합니다.
+variant를 바꾸려면 `model` 필드만 변경합니다.
 
 ```json
 {
-  "model": "github-copilot/gpt-5.6-luna"
+  "model": "openai/gpt-5.6-terra"
 }
 ```
 
@@ -97,11 +91,11 @@ Token Station은 GPT-5.6 `cache_write_tokens`를 cache-creation bucket으로 정
 
 Claude Fable 5는 long-running coding agent의 자연스러운 비교 대상입니다. Token Station에서는 1M context window와 더 높은 $10/$50 price profile로 설정되어 있습니다.
 
-GPT-5.6은 다른 운영 형태를 제공합니다. OpenAI-native route, Codex/Copilot surface, 그리고 같은 family 안의 여러 price tier입니다.
+GPT-5.6은 다른 운영 형태를 제공합니다. OpenAI-native route, Codex 스타일 surface, 그리고 같은 family 안의 여러 price tier입니다.
 
 시작점은 간단합니다.
 
-- OpenAI-native route, Codex나 Copilot surface, 또는 high-volume step에 더 저렴한 tier가 필요하면 GPT-5.6 패밀리를 선택합니다. Sol, Terra, Luna는 위에서 설명한 대로 작업별로 고릅니다.
+- OpenAI-native route, Codex 스타일 surface, 또는 high-volume step에 더 저렴한 tier가 필요하면 GPT-5.6 패밀리를 선택합니다. Sol, Terra, Luna는 위에서 설명한 대로 작업별로 고릅니다.
 - Anthropic의 long-running-agent behavior와 1M context가 필요하고 더 높은 가격을 감수한다면 Claude Fable 5를 사용합니다.
 - workflow fit이 model brand보다 중요하면 Token Station 안에서 비교합니다.
 
@@ -117,6 +111,6 @@ GMI Cloud와 AWS Bedrock OpenAI catalog는 당시 공개 catalog에 GPT-5.6이
 
 이미 Token Station을 사용하고 있다면 GPT-5.6은 coding-agent workflow에 추가할 수 있는 새로운 route family입니다.
 
-direct OpenAI route로 API check를 하고, Codex에서는 같은 `openai/` route를 설정해 terminal coding task를 테스트하고, GitHub Copilot catalog에 의존하는 workflow라면 Copilot route를 시험할 수 있습니다.
+direct OpenAI route로 API check를 하고, Codex에서는 같은 `openai/` route를 설정해 terminal coding task를 테스트할 수 있습니다.
 
 [Token Station 사용해 보기](https://models.bytefuture.ai/intro.html)
diff --git a/src/content/writings/zh/gpt-5-6-token-station.md b/src/content/writings/zh/gpt-5-6-token-station.md
@@ -2,7 +2,7 @@
 slug: gpt-5-6-token-station
 lang: zh
 title: "GPT-5.6 已接入 Token Station：在你的 coding agent 路由里直接试用"
-summary: "Token Station 现在支持 GPT-5.6，覆盖 OpenAI-compatible API、Codex 和 Copilot 等 coding-agent 路由。用一个 endpoint 比较 Sol、Terra、Luna 和 Claude Fable 5 在真实工作流里的表现。"
+summary: "Token Station 现在支持 GPT-5.6，覆盖 OpenAI-compatible API 和 Codex 风格的 coding-agent 路由。用一个 endpoint 比较 Sol、Terra、Luna 和 Claude Fable 5 在真实工作流里的表现。"
 category: product
 date: 2026-07-13
 cta: https://models.bytefuture.ai/intro.html
@@ -11,7 +11,7 @@ cover: blog/gpt-5-6-token-station-cover.png
 
 GPT-5.6 已经接入 Token Station。
 
-对 coding-agent 团队来说，真正的价值在于 GPT-5.6 可以通过开发者已经在用的 route 来测试：直接的 OpenAI-compatible API、OpenAI Codex 风格工作流，以及 GitHub Copilot 已发布支持的 route。
+对 coding-agent 团队来说，真正的价值在于 GPT-5.6 可以通过开发者已经在用的 route 来测试：直接的 OpenAI-compatible API 和 OpenAI Codex 风格工作流。
 
 这让 GPT-5.6 不只是一个发布新闻，而是一个可以路由、比较、逐步采用的模型选择，并且不需要重建你的 agent stack。
 
@@ -24,12 +24,6 @@ Token Station 暴露直接 OpenAI-compatible GPT-5.6 route：
 - `openai/gpt-5.6-terra`
 - `openai/gpt-5.6-luna`
 
-以及 GitHub Copilot 已发布支持的 route：
-
-- `github-copilot/gpt-5.6-sol`
-- `github-copilot/gpt-5.6-terra`
-- `github-copilot/gpt-5.6-luna`
-
 OpenAI Codex 风格的工作流使用的就是上面这些 `openai/` route，所以不需要单独配置一个 Codex route。
 
 结果很简单：你可以从匹配工作流的 surface 测试同一个模型家族，而不是把每个 provider interface 都当成一个单独集成项目。
@@ -50,11 +44,11 @@ curl https://models.bytefuture.ai/v1/chat/completions \
   }'
 ```
 
-想试 Copilot route：
+想切换变体，只改 `model` 字段：
 
 ```json
 {
-  "model": "github-copilot/gpt-5.6-luna"
+  "model": "openai/gpt-5.6-terra"
 }
 ```
 
@@ -99,11 +93,11 @@ Token Station 里的实用价格框架：
 
 Claude Fable 5 仍然是 long-running coding agent 的自然对比对象。它在 Token Station 中配置为 1M context window，并且价格是更高的 $10/$50 profile。
 
-GPT-5.6 的操作形态不同：OpenAI-native route、Codex 和 Copilot surface，以及同一模型家族里的多个价格 tier。
+GPT-5.6 的操作形态不同：OpenAI-native route、Codex 风格 surface，以及同一模型家族里的多个价格 tier。
 
 一个简单起点：
 
-- 想要 OpenAI-native route、Codex 或 Copilot surface，或者给高频步骤用更便宜的 tier，就选 GPT-5.6 家族；Sol、Terra、Luna 按上面说的按任务挑。
+- 想要 OpenAI-native route、Codex 风格 surface，或者给高频步骤用更便宜的 tier，就选 GPT-5.6 家族；Sol、Terra、Luna 按上面说的按任务挑。
 - 明确想要 Anthropic 的 long-running-agent 行为和 1M context，并愿意支付更高价格，就用 Claude Fable 5。
 - 当 workflow fit 比模型品牌更重要时，把它们放在 Token Station 里比较。
 
@@ -119,7 +113,7 @@ GMI Cloud 和 AWS Bedrock OpenAI catalog 没有添加，因为它们当时的公
 
 如果你已经使用 Token Station，GPT-5.6 现在就是另一个可以放进 coding-agent workflow 测试的 route family。
 
-先用直接 OpenAI route 做简单 API 检查；在 Codex 里配置同一个 `openai/` route 跑终端 coding task；如果 workflow 依赖 GitHub Copilot 的 supported model catalog，就试 Copilot route。
+先用直接 OpenAI route 做简单 API 检查；在 Codex 里配置同一个 `openai/` route 跑终端 coding task。
 
 Token Station 让你在一个地方比较这些 route，而不用为每次模型发布重写 agent stack。