Add Zoo Code to the third-party coding agent API whitelist

What feature would you like to see?

Description

Zoo Code (the active community successor to Roo Code) is currently rejected by the Kimi Code API with a 403 error.

Background

Roo Code has been on the Kimi Code whitelist for some time and works correctly. However, the Roo Code project was officially discontinued and archived on May 15, 2026. Zoo Code was created as the direct continuation fork and is now the primary migration path for existing Roo Code users.

The problem

Starting with Zoo Code v3.56.0, the extension updated its OpenAI-compatible client identifier. It no longer matches the whitelist entry that previously allowed Roo Code (and by extension, early Zoo Code builds) through. As a result, all API requests from Zoo Code now fail with:

Provider Error 403 Unauthorized: Your API key is valid, but the provider refused to complete this request

Kimi Code's API currently returns:

{
  "error": {
    "type": "access_terminated_error",
    "message": "Kimi For Coding is currently only available for Coding Agents such as Kimi CLI, Claude Code, Roo Code, Kilo Code, etc."
  }
}

Request

Please add Zoo Code to the supported third-party coding agent whitelist.

Why this is straightforward

• Zoo Code is built directly on Roo Code's codebase and is API-compatible in every meaningful way (same tool-use patterns, streaming behavior, and request structure).
• Roo Code is no longer maintained; whitelisting Roo but not its successor leaves paying subscribers without a supported upgrade path.

More Info

• Zoo Code Documentation: docs.zoocode.dev
• Zoo Code GitHub: Zoo Code
• Zoo Code VSCode Extension: Zoo Code - Extension Marketplace
• Kimi Code Docs referencing Roo Code: Third-Party Coding Agents — Roo Code

Additional information

No response

Start by locating the existing Roo Code whitelist entry and the code path that handles third-party agent identifiers. Add Zoo Code alongside the supported agent entries, then verify with a Zoo Code v3.56.0 request that the previous 403 response is resolved.