@zvada/agent-server 0.3.5 → 0.3.6

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.3.6
+
+- Unsupported Codex app-server requests now receive an explicit protocol error.
+  Previously, requests such as MCP elicitations were treated as file-edit
+  approvals and could leave a turn waiting in the permission broker. Command
+  and file approvals and host-managed credential refresh keep their existing behavior.
+
 ## 0.3.5
 
 - Switching Codex ChatGPT accounts or API keys now recreates the native process

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@zvada/agent-server",
-	"version": "0.3.5",
+	"version": "0.3.6",
 	"description": "Harness-agnostic agent execution engine: run Claude Code, Codex (SDK/CLI + app-server), and any ACP agent behind one interface with a normalized event stream, multi-turn sessions, and resume. Root export is the wire contract; /core, /server, /client are the seats.",
 	"license": "MIT",
 	"type": "module",

package/src/core/agents/codex-app-server/codex-app-server-agent.ts

@@ -395,6 +395,16 @@ export class CodexAppServerAgent extends BaseAgent {
 					chatgptPlanType: tokens.chatgptPlanType ?? null,
 				};
 			}
+			// Elicitations and other server requests have their own response shapes.
+			// Sending them to the approval broker can leave a turn waiting forever.
+			if (
+				method !== "item/commandExecution/requestApproval" &&
+				method !== "item/fileChange/requestApproval" &&
+				method !== "execCommandApproval" &&
+				method !== "applyPatchApproval"
+			) {
+				throw new Error(`Unsupported Codex server request: ${method}`);
+			}
 			const requestThread = params.threadId ?? params.conversationId;
 			const v2 = method.startsWith("item/");
 			const decline = v2 ? { decision: "decline" } : { decision: "denied" };