Skip to content
NorviTech Helios
Browse the Helios guide

Helios / User guide / Kimi Code membership

Kimi Code membership

Connect Kimi Code membership to Helios through the native ACP integration, sign in, refresh models and understand thinking and permission limits.

Helios 0.114.4 · Source reference ↗

Install Kimi Code

Use the current Kimi Code CLI instructions from Moonshot AI. Helios’s integration requires Kimi Code 2.3.2 or newer, with a runnable kimi executable.

kimi --version
kimi login

Complete the membership device-code sign-in in your browser. Kimi owns and refreshes its credentials. HELIOS_KIMI_BINARY can select a specific local executable.

Verify membership and models

Check Settings → Accounts, then refresh Settings → Providers → Kimi. Helios performs a tool-free ACP handshake and lists the models the account reports.

Helios uses kimi acp and the membership route. It does not silently fall back to OpenRouter or a metered API. Selecting a Kimi model through OpenRouter is a different provider path.

Start and inspect a task

  1. Choose a project folder with Ctrl+Shift+N.
  2. Select a discovered Kimi model.
  3. Inspect the model’s thinking and native permission controls.
  4. Ask for an explanation of a named file before allowing a small edit.
  5. Read the tool activity, then inspect Changes and run the relevant check.

Use supported native features

The integration includes resume, a fork from the conversation head, live-discovered models and thinking options, native image/resource input, tool activity and approvals.

Kimi-configured MCP servers and selected Helios integrations can be forwarded when supported by the installed ACP runtime. Supported Helios browser tools are included in that integration path.

Understand permissions and quota limits

Never ask and Bypass both map to Kimi’s native YOLO setting. Never ask must not be treated as a restricted refusal mode on this provider. Read the active native policy before continuing.

ACP does not currently provide a membership quota-window API to Helios. Audio is also not exposed through this integration. Helios does not invent quota percentages or subscription-spend estimates.

If membership is unverified or the model list is empty, check native sign-in, CLI version and the provider refresh result. The Kimi integration reference documents protocol-specific recovery.