chore: finish the brand sweep in extension release notes and test fixtures

Complete the identity rename in the VS Code extension changelog: the 0.6.x
blocks still carried the old product name, repository links, SDK scope, home
environment variable and setting keys that the newer entries in the same file
already use in their current form.

Drop a stale release note describing a managed OAuth provider id the product
does not ship.

Rename arbitrary model ids in the extension test fixtures to neutral
placeholders.

Author: elkaix

apps/vscode/CHANGELOG.md

@@ -114,25 +114,25 @@
 
 ### Patch Changes
 
-- [#2326](https://github.com/MoonshotAI/kimi-code/pull/2326) [`302b2cd`](https://github.com/MoonshotAI/kimi-code/commit/302b2cd680e0ec66f68b4572238de84ce311c5f4) Thanks [@gaoyuan1223m](https://github.com/gaoyuan1223m)! - Fix only the first question being answerable when the agent asked multiple questions at once; each question is now answered one by one and submitted together.
+- [#2326](https://github.com/PyModel/pythinker-code/pull/2326) [`302b2cd`](https://github.com/PyModel/pythinker-code/commit/302b2cd680e0ec66f68b4572238de84ce311c5f4) Thanks [@gaoyuan1223m](https://github.com/gaoyuan1223m)! - Fix only the first question being answerable when the agent asked multiple questions at once; each question is now answered one by one and submitted together.
 
 ## 0.6.6
 
 ### Patch Changes
 
-- [#2393](https://github.com/MoonshotAI/kimi-code/pull/2393) [`6d0a046`](https://github.com/MoonshotAI/kimi-code/commit/6d0a046488edda56219961b253c4787abae7a113) Thanks [@wbxl2000](https://github.com/wbxl2000)! - Fix new users getting stranded on "Model setup required" with no way back to sign-in when the first login finishes authorization but fails to complete model setup; the screen now offers a path back to the sign-in page so login can be retried.
-- [#2402](https://github.com/MoonshotAI/kimi-code/pull/2402) [`0f3b106`](https://github.com/MoonshotAI/kimi-code/commit/0f3b106c4260ad626f66bc5c457a535d3163f2bc) Thanks [@wbxl2000](https://github.com/wbxl2000)! - Reword the sign-in waiting message from "Waiting for authorization" to "Waiting for authentication".
+- [#2393](https://github.com/PyModel/pythinker-code/pull/2393) [`6d0a046`](https://github.com/PyModel/pythinker-code/commit/6d0a046488edda56219961b253c4787abae7a113) Thanks [@wbxl2000](https://github.com/wbxl2000)! - Fix new users getting stranded on "Model setup required" with no way back to sign-in when the first login finishes authorization but fails to complete model setup; the screen now offers a path back to the sign-in page so login can be retried.
+- [#2402](https://github.com/PyModel/pythinker-code/pull/2402) [`0f3b106`](https://github.com/PyModel/pythinker-code/commit/0f3b106c4260ad626f66bc5c457a535d3163f2bc) Thanks [@wbxl2000](https://github.com/wbxl2000)! - Reword the sign-in waiting message from "Waiting for authorization" to "Waiting for authentication".
 
-- Updated dependencies [[`40172c7`](https://github.com/MoonshotAI/kimi-code/commit/40172c7ca96ca981b043b793588dd32e898979fa)]:
-  - @moonshot-ai/kimi-code-sdk@0.15.0
+- Updated dependencies [[`40172c7`](https://github.com/PyModel/pythinker-code/commit/40172c7ca96ca981b043b793588dd32e898979fa)]:
+  - @pymodel/pythinker-code-sdk@0.15.0
 
 ## 0.6.5
 
 ### Patch Changes
 
-- [#1994](https://github.com/MoonshotAI/kimi-code/pull/1994) [`beeb964`](https://github.com/MoonshotAI/kimi-code/commit/beeb964393c8f9a38c2b1e2273e4415fc434b16d) Thanks [@RealKai42](https://github.com/RealKai42)! - Reduce webview streaming re-render churn: settled assistant messages no longer re-render on every streaming delta, and local images over 10MB are no longer inlined into the webview DOM.
-- Updated dependencies [[`ec88d35`](https://github.com/MoonshotAI/kimi-code/commit/ec88d352e8f4dc5e8ffd1212f016138458f69893), [`b5efba7`](https://github.com/MoonshotAI/kimi-code/commit/b5efba7abcaf4041f81ec520097a61e6546e8c50), [`ce0e3ce`](https://github.com/MoonshotAI/kimi-code/commit/ce0e3ceb04223bdaad8e8931bad46eff561055b6), [`e458323`](https://github.com/MoonshotAI/kimi-code/commit/e45832398d0d9cad98dbad1cbf1e5b103a20aace)]:
-  - @moonshot-ai/kimi-code-sdk@0.14.0
+- [#1994](https://github.com/PyModel/pythinker-code/pull/1994) [`beeb964`](https://github.com/PyModel/pythinker-code/commit/beeb964393c8f9a38c2b1e2273e4415fc434b16d) Thanks [@RealKai42](https://github.com/RealKai42)! - Reduce webview streaming re-render churn: settled assistant messages no longer re-render on every streaming delta, and local images over 10MB are no longer inlined into the webview DOM.
+- Updated dependencies [[`ec88d35`](https://github.com/PyModel/pythinker-code/commit/ec88d352e8f4dc5e8ffd1212f016138458f69893), [`b5efba7`](https://github.com/PyModel/pythinker-code/commit/b5efba7abcaf4041f81ec520097a61e6546e8c50), [`ce0e3ce`](https://github.com/PyModel/pythinker-code/commit/ce0e3ceb04223bdaad8e8931bad46eff561055b6), [`e458323`](https://github.com/PyModel/pythinker-code/commit/e45832398d0d9cad98dbad1cbf1e5b103a20aace)]:
+  - @pymodel/pythinker-code-sdk@0.14.0
 
 ## 0.6.4
 
@@ -168,7 +168,7 @@
 - A core error arriving in the middle of a turn no longer corrupts the active
   turn; the turn now ends cleanly with an error instead of leaving the chat in
   a broken state.
-- Kimi sign-in and connection failures now include the underlying transport
+- Pythinker sign-in and connection failures now include the underlying transport
   cause (for example DNS or connection refused) instead of a generic error.
 - Closed several FetchURL SSRF bypasses and the DNS-rebinding window.
 - Tool calls interrupted mid-stream are now recorded and closed, so they no
@@ -179,50 +179,50 @@
 ### Fixed
 
 - The **Sign in** action in the settings (gear) menu now actually starts the
-  Kimi login flow and shows an error toast when sign-in fails, instead of
+  Pythinker login flow and shows an error toast when sign-in fails, instead of
   silently doing nothing.
 
 ## 0.6.0
 
 ### Breaking
 
 - Raised the minimum supported editor version to VS Code 1.100.0.
-- Legacy Kimi Code OAuth credentials and MCP OAuth credentials are deliberately
-  not migrated. Sign in to Kimi Code again and re-authorize affected MCP
+- Legacy Pythinker Code OAuth credentials and MCP OAuth credentials are deliberately
+  not migrated. Sign in to Pythinker Code again and re-authorize affected MCP
   servers after upgrading.
-- Removed the `kimi.executablePath` and `kimi.environmentVariables` settings.
-  The old `kimi.environmentVariables.KIMI_SHARE_DIR` value is consulted only to
+- Removed the `pythinker.executablePath` and `pythinker.environmentVariables` settings.
+  The old `pythinker.environmentVariables.PYTHINKER_SHARE_DIR` value is consulted only to
   discover legacy data during migration; it is not applied to the new runtime.
-  The system-level `KIMI_CODE_HOME` environment variable remains supported.
+  The system-level `PYTHINKER_CODE_HOME` environment variable remains supported.
 
 ### Changed
 
-- Replaced the legacy Python/stdio runtime with the in-process Kimi Code Node
-  SDK. The extension no longer downloads or starts a separate Kimi executable.
-- The in-process engine is the same one that powers the Kimi Code CLI, so the
+- Replaced the legacy Python/stdio runtime with the in-process Pythinker Code Node
+  SDK. The extension no longer downloads or starts a separate Pythinker executable.
+- The in-process engine is the same one that powers the Pythinker Code CLI, so the
   agent gains CLI-parity capabilities beyond the legacy runtime, including
   parallel subagent swarms, background tasks, and long-running goal runs.
 - Added an opt-in legacy migration prompt on the first launch that detects data
   from version 0.5.x. The migration copies or merges supported data into the
-  current Kimi Code home and does not delete the legacy source. If migration is
-  skipped or needs to be retried, run **Kimi Code: Migrate Legacy Data** from the
+  current Pythinker Code home and does not delete the legacy source. If migration is
+  skipped or needs to be retried, run **Pythinker Code: Migrate Legacy Data** from the
   Command Palette.
-- When VS Code and the Kimi Code terminal app resolve to the same
-  `KIMI_CODE_HOME`, they use the same configuration and session storage. Running
+- When VS Code and the Pythinker Code terminal app resolve to the same
+  `PYTHINKER_CODE_HOME`, they use the same configuration and session storage. Running
   the same session concurrently from multiple processes is not supported or
   protected by cross-process locking.
 - The model picker groups models by provider when multiple providers are
   configured, keeps provider identity when display names match, and recognizes
   adaptive-thinking metadata. A configured custom default provider no longer
-  requires dismissing the Kimi account login screen on every launch.
+  requires dismissing the Pythinker account login screen on every launch.
 - The file changes panel and Undo actions use extension-maintained baselines.
-  Files changed through Kimi's Write and Edit operations are tracked on a
+  Files changed through Pythinker's Write and Edit operations are tracked on a
   best-effort basis. File deletions performed inside Bash are not tracked by
   this baseline and therefore cannot be restored by the panel's Undo action.
 
 ### Fixed
 
-- The `kimi.yoloMode` setting now reaches the permission engine: enabling it
+- The `pythinker.yoloMode` setting now reaches the permission engine: enabling it
   maps to the core `yolo` permission mode and takes effect when a session
   attaches, including sessions that previously stored a disabled auto-approve
   state.

apps/vscode/test/bridge-handler.test.ts

@@ -692,23 +692,23 @@ describe("Webview config saves (thinking effort persistence parity with the TUI)
 
   function mockConfig(thinking?: { enabled?: boolean; effort?: string }) {
     host.harness.getConfig.mockResolvedValue({
-      defaultModel: "kimi/reasoning",
+      defaultModel: "acme/reasoning",
       thinking: thinking ?? { enabled: true, effort: "high" },
-      models: { "kimi/reasoning": effortModel },
+      models: { "acme/reasoning": effortModel },
     } as never);
   }
 
   it("persists a non-top effort as the global default", async () => {
     mockConfig({ enabled: false, effort: "low" });
 
     const result = await bridge.handle(
-      { id: "rpc-1", method: Methods.SaveConfig, params: { model: "kimi/reasoning", thinking: true, effort: "high" } },
+      { id: "rpc-1", method: Methods.SaveConfig, params: { model: "acme/reasoning", thinking: true, effort: "high" } },
       "view-1",
     );
 
     expect(result).toEqual({ id: "rpc-1", result: { ok: true } });
     expect(host.harness.setConfig).toHaveBeenCalledWith({
-      defaultModel: "kimi/reasoning",
+      defaultModel: "acme/reasoning",
       thinking: { enabled: true, effort: "high" },
     });
   });
@@ -717,12 +717,12 @@ describe("Webview config saves (thinking effort persistence parity with the TUI)
     mockConfig({ enabled: false });
 
     await bridge.handle(
-      { id: "rpc-1", method: Methods.SaveConfig, params: { model: "kimi/reasoning", thinking: true, effort: "max" } },
+      { id: "rpc-1", method: Methods.SaveConfig, params: { model: "acme/reasoning", thinking: true, effort: "max" } },
       "view-1",
     );
 
     expect(host.harness.setConfig).toHaveBeenCalledWith({
-      defaultModel: "kimi/reasoning",
+      defaultModel: "acme/reasoning",
       thinking: { enabled: true },
     });
   });
@@ -781,12 +781,12 @@ describe("Webview config saves (thinking effort persistence parity with the TUI)
     mockConfig({ enabled: false, effort: "high" });
 
     await bridge.handle(
-      { id: "rpc-1", method: Methods.SaveConfig, params: { model: "kimi/reasoning", thinking: true, effort: "high", effortChanged: false } },
+      { id: "rpc-1", method: Methods.SaveConfig, params: { model: "acme/reasoning", thinking: true, effort: "high", effortChanged: false } },
       "view-1",
     );
 
     expect(host.harness.setConfig).toHaveBeenCalledWith({
-      defaultModel: "kimi/reasoning",
+      defaultModel: "acme/reasoning",
       thinking: { enabled: true },
     });
   });
@@ -795,7 +795,7 @@ describe("Webview config saves (thinking effort persistence parity with the TUI)
     mockConfig({ enabled: true, effort: "high" });
 
     await bridge.handle(
-      { id: "rpc-1", method: Methods.SaveConfig, params: { model: "kimi/reasoning", thinking: true, effort: "high" } },
+      { id: "rpc-1", method: Methods.SaveConfig, params: { model: "acme/reasoning", thinking: true, effort: "high" } },
       "view-1",
     );
 

apps/vscode/test/pythinker-runtime.test.ts

@@ -71,7 +71,7 @@ function createFakeSession(
   let closes = 0;
   let promptImpl: (input: string | PromptInput) => Promise<void> = async () => {};
   let status: SessionStatus = {
-    model: initial.model ?? "kimi-test",
+    model: initial.model ?? "acme-test",
     thinkingEffort: initial.thinkingEffort ?? "off",
     permission: initial.permission ?? "manual",
     planMode: initial.planMode ?? false,
@@ -242,7 +242,7 @@ function openOptions(overrides: Partial<OpenSessionOptions> = {}): OpenSessionOp
   return {
     webviewId: "view-1",
     workDir: "/workspace",
-    model: "kimi-test",
+    model: "acme-test",
     effort: "off",
     yoloMode: false,
     ...overrides,
@@ -500,7 +500,7 @@ describe("Pythinker runtime (owns shared SDK sessions for Webviews)", () => {
       log: () => undefined,
     });
     sdk.addSession("saved-1", "/workspace", {
-      model: "kimi-test",
+      model: "acme-test",
       thinkingEffort: "max",
       planMode: true,
     });
@@ -514,7 +514,7 @@ describe("Pythinker runtime (owns shared SDK sessions for Webviews)", () => {
         // The permission mode rides along: the chat badge is the only place the
         // user can see which mode a toggle command just landed on.
         payload: {
-          model: "kimi-test",
+          model: "acme-test",
           thinking_effort: "max",
           plan_mode: true,
           permission: "manual",
@@ -551,7 +551,7 @@ describe("Pythinker runtime (owns shared SDK sessions for Webviews)", () => {
       data: {
         type: "StatusUpdate",
         payload: {
-          model: "kimi-test",
+          model: "acme-test",
           thinking_effort: "off",
           plan_mode: false,
           permission: "yolo",

apps/vscode/test/replay-adapter.test.ts

@@ -61,7 +61,7 @@ function resumedAgent(
     type: options.type ?? "main",
     config: {
       cwd: "/workspace",
-      modelAlias: options.modelAlias ?? "kimi-test",
+      modelAlias: options.modelAlias ?? "acme-test",
       modelCapabilities: {
         image_in: true,
         video_in: true,
@@ -93,7 +93,7 @@ describe("replay adapter (renders the public SDK resume state for the Webview)",
 
     expect(replayToWebviewEvents(agent, "session-1")[0]).toMatchObject({
       type: "StatusUpdate",
-      payload: { model: "kimi-test" },
+      payload: { model: "acme-test" },
     });
   });
 

docs/release-notes/changelog.md

@@ -70,7 +70,6 @@ This page documents the changes in each Pythinker Code CLI release.
 
 ### Polish
 
-- Rename the managed OAuth provider so it is named after the platform that serves it rather than reading as a first-party service: the provider id is now `managed:kimi-code`, its models are aliased `kimi-code/*`, and its credentials are stored under `oauth/kimi-code`.
 - Add an SDK routine that imports a catalog provider and its models into the persisted config, and use it for the CLI provider import so both entry points preserve existing defaults the same way.
 
 ## 0.8.1 (2026-08-05)