buildwithnexusv0.21.0
Menu

Editors

bwn acp speaks the Agent Client Protocol version 1 on stdin and stdout, so Zed, JetBrains IDEs and Neovim plugins that run ACP agents can drive bwn. The editor shows the streamed reply, each tool call with its diff, the plan, and the approval questions.

Add it to an editor

In Zed, add this to settings.json, then pick buildwithnexus from the Agent Panel's new-thread menu:

{
  "agent_servers": {
    "buildwithnexus": {
      "type": "custom",
      "command": "bwn",
      "args": ["acp"],
      "env": {}
    }
  }
}

Other ACP clients take the same command and arguments. bwn uses the provider, model and key you set up in the terminal (~/.buildwithnexus). Put an API key or NEXUS_HOME in env to use others. Options from Headless go in args, for example ["acp", "--permission-mode", "accept-edits"]. If the editor cannot find bwn, give the full path that command -v bwn prints.

bwn acp takes nothing else on the command line. Anything after it exits 2, because the editor talks to bwn on stdin. One process serves one folder and runs one prompt at a time. Helpers a reply starts run one after another, so the editor can show each one's calls under it. Anything bwn prints besides the protocol goes to stderr, which the editor keeps as the agent's log. A line that is not UTF-8 gets a JSON-RPC parse error, and the server keeps serving.

Approvals, trust and modes

See Permissions & hooks for what each mode and hook does.

Files, sessions and MCP