Skip to content

Using NexgenK CLI in IDEs ​

NexgenK CLI 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 NexgenK CLI is installed and you have completed the login setup.

The ACP server is exposed as the nexgenk 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 nexgenk is not in a system directory like /usr/local/bin, use the absolute path in your IDE configuration. Run which nexgenk in a terminal to find the active path.

Using NexgenK CLI 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": {
    "NexgenK CLI": {
      "type": "custom",
      "command": "nexgenk",
      "args": ["acp"],
      "env": {}
    }
  }
}

Configuration fields:

  • type: fixed value "custom"
  • command: path to the NexgenK CLI executable. If nexgenk is not on PATH, use the full path (e.g. /Users/you/.local/bin/nexgenk).
  • 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 NexgenK CLI ACP subprocess using the configuration above. MCP servers declared in Zed's agent_servers section are also forwarded to the nexgenk side via the ACP protocol.

Using NexgenK CLI 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.

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

json
{
  "agent_servers": {
    "NexgenK CLI": {
      "command": "~/.local/bin/nexgenk",
      "args": ["acp"],
      "env": {}
    }
  }
}

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

Using NexgenK CLI in Paseo ​

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

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

json
{
  "agents": {
    "providers": {
      "nexgenk": {
        "extends": "acp",
        "label": "NexgenK CLI",
        "command": ["nexgenk", "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 nexgenk 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 nexgenk in a terminal to complete login, then restart the IDE.
  • MCP tools not visible: check the nexgenk acp reference capability table to confirm that the MCP transport type configured in your IDE is supported. The NexgenK CLI ACP server currently supports http, stdio, and sse transports; acp transport MCP servers are silently dropped and a warning is written to the log.

Next steps ​