ACP protocol requires login - is Kimi model mandatory?

Question

When using the ACP protocol (kimi-code acp), it seems to require authentication/login before it can be used.

Is it currently mandatory to use Kimi's own model to use the ACP protocol? Or is there a way to use the ACP transport with other model providers (e.g. OpenAI-compatible endpoints) without a Kimi account?

Context

We're building an agent orchestration platform that supports multiple CLI agent backends via ACP. We'd like to integrate kimi-code as an ACP provider, but the login requirement creates friction for users who may not have a Kimi account but still want to use kimi-code's ACP capabilities with their own model API keys.

Expected behavior

Ideally the ACP protocol layer would be usable independently of the model provider, similar to how other agent CLIs allow configuring custom API endpoints.

Actual behavior

Running kimi-code acp appears to require prior authentication, limiting usage to Kimi model users.

Is this by design, or are there plans to support model-agnostic ACP usage?

Start by reproducing the authentication requirement with kimi-code acp and trace the ACP entry point to see where login and model-provider configuration are enforced. Determine whether the requested model-independent transport is feasible, then define tests or documentation that establish the supported provider and authentication behavior as done.