From 7ae98888d269a9eb41c58f5c52a71c5299125da6 Mon Sep 17 00:00:00 2001
From: Drewry Pope <drewrypope@gmail.com>
Date: Thu, 29 Oct 2026 21:19:20 -0500
Subject: [PATCH] fix(openclaw): remove opencode-acp entry that cannot evaluate

The nix-openclaw generated schema makes the acp runtime branch of an agent entry unreachable (oneOf of submodules, pinned nixpkgs), so the entry fails the whole NixOS evaluation and blocks every switch. Analysis + minimal repro: #2509. Restore tracked by #2256. The ACP capability (acp.enabled, allowedAgents, acpx plugin) is unaffected.
---
 home/openclaw/default.nix | 30 +++++++++---------------------
 1 file changed, 9 insertions(+), 21 deletions(-)

diff --git a/home/openclaw/default.nix b/home/openclaw/default.nix
index 88413a7ce..a2100553d 100644
--- a/home/openclaw/default.nix
+++ b/home/openclaw/default.nix
@@ -292,27 +292,15 @@ in
           main = {
             name = "OpenClaw (laptop node)";
           };
-          # ACP-runtime agent (#2229 mechanism 1): this agent's turns run
-          # in the OpenCode harness over acpx, so OpenClaw can dispatch
-          # work to OpenCode as a standing capability, not only from
-          # chat-channel sessions. OpenCode's own default model is the
-          # workhorse route (opencode-route/workhorse); a run can set the
-          # route explicitly. Mode "oneshot" = one fresh ACP session per
-          # task. Heartbeat cadence off: dispatch is explicit, this agent
-          # must never wake itself into OpenCode hourly.
-          opencode-acp = {
-            name = "OpenCode (ACP harness)";
-            heartbeat.every = "0m";
-            runtime = {
-              type = "acp";
-              acp = {
-                agent = "opencode";
-                backend = "acpx";
-                mode = "oneshot";
-                cwd = homeDir;
-              };
-            };
-          };
+          # The ACP-runtime agent entry (opencode-acp, #2229 mechanism 1)
+          # is removed for now: the nix-openclaw generated schema types an
+          # entry's runtime as a oneOf of two submodules, and under the
+          # pinned nixpkgs the acp branch is unreachable, so any entry
+          # using it fails the whole configuration evaluation. Full
+          # analysis and the minimal reproduction: code#2509. Restore the
+          # entry (tracked by #2256) once the schema can express it. The
+          # ACP capability itself (acp block below: enabled, allowedAgents,
+          # acpx plugin) is unaffected.
         };
       };