Kiki

English

简体中文

English

简体中文

Appearance

Using Kiki in IDEs ​

Kiki supports integration into IDEs via the Agent Client Protocol (ACP), letting you use AI-assisted coding directly inside your editor.

Prerequisites ​

Before configuring your IDE, make sure Kiki is installed and you have completed the login setup.

The ACP adapter is exposed as the kiki acp subcommand. The IDE launches it as a child process and communicates over stdin/stdout using JSON-RPC. Each time the IDE creates a session, the CLI reuses its existing authentication state — no need to log in again.

Path note

Child processes launched from an IDE GUI on macOS typically do not inherit the terminal shell's PATH. If kiki is not in a system directory like /usr/local/bin, use the absolute path in your IDE configuration. Run which kiki in a terminal to find the active path.

Using Kiki in Zed ​

Zed is a modern editor with native ACP support.

Add the following to Zed's config file at ~/.config/zed/settings.json:

json
{
  "agent_servers": {
    "Kiki": {
      "type": "custom",
      "command": "kiki",
      "args": ["acp"],
      "env": {}
    }
  }
}

Configuration fields:

  • type: fixed value "custom"
  • command: path to the Kiki executable. If kiki is not on PATH, use the full path (e.g. /Users/you/.local/bin/kiki).
  • args: startup arguments. The acp subcommand switches the CLI into ACP mode.
  • env: additional environment variables; usually leave this empty. Zed injects a default environment automatically.

After saving, open a new conversation in Zed's Agent panel and it will launch a Kiki ACP subprocess using the configuration above. MCP servers declared in Zed's agent_servers section are also forwarded to the kiki side via the ACP protocol.

Using Kiki in JetBrains IDEs ​

JetBrains IDEs (IntelliJ IDEA, PyCharm, WebStorm, etc.) support ACP through the AI chat plugin.

If you do not have a JetBrains AI subscription, you can enable llm.enable.mock.response in the Registry to access the AI chat panel in ACP-only scenarios. Press Shift twice and search for "Registry" to open it.

WARNING

With llm.enable.mock.response enabled, the AI panel returns canned fake data, not real model output — it only helps you verify the panel wiring before connecting Kiki. Turn it off once the panel works, or you will keep seeing fake replies.

In the AI chat panel menu, click Configure ACP agents and add the following configuration:

json
{
  "agent_servers": {
    "Kiki": {
      "command": "~/.local/bin/kiki",
      "args": ["acp"],
      "env": {}
    }
  }
}

JetBrains is strict about the command field — always use an absolute path, which you can get by running which kiki in a terminal. After saving, Kiki will appear in the AI chat's agent selector.

Using Kiki in Paseo ​

Paseo is a self-hosted orchestrator that runs and supervises agent CLIs from your desktop, web, and mobile. It connects to Kiki over ACP, the same way an IDE does.

Pick Kiki from Paseo's built-in ACP provider catalog, or add a custom provider in ~/.paseo/config.json:

json
{
  "agents": {
    "providers": {
      "kiki": {
        "extends": "acp",
        "label": "Kiki",
        "command": ["kiki", "acp"]
      }
    }
  }
}

Paseo's generic ACP adapter does not drive the login flow, so complete the terminal login first (see Prerequisites) — otherwise session creation fails with Authentication required.

Troubleshooting ​

  • Session disconnects immediately / IDE shows "agent exited": usually a wrong command path or a missing login. Run kiki acp in a terminal first to verify — if it blocks waiting for stdin, the CLI itself is fine and the problem is in the IDE configuration; if it exits immediately with an error, follow the error message (most commonly you need to run /login).
  • IDE shows "auth required": the CLI has no usable authentication token. Exit the IDE, run kiki in a terminal to complete login, then restart the IDE.
  • MCP tools not visible: the kiki acp adapter accepts http and sse transports, and stdio only when the IDE is started with --allow-client-stdio-mcp. An acp-transport server is discarded with a warning in the log. See MCP Forwarding.

Next steps ​