Summary

• Problem: configured Computer Use MCP approval elicitations can arrive without a JSON-object requestedSchema, and the app-server request handler returned the asynchronous elicitation bridge promise without awaiting it, letting request-response bookkeeping/finally run before the bridge settled.
• Solution: keep the exact configured MCP server-name boundary and form-mode guard, normalize missing or non-object Computer Use schemas to an empty object schema, and use return await handleCodexAppServerElicitationRequest(...) so request-response bookkeeping/finally waits for the approval bridge result.
• What changed: schema-less Computer Use form elicitations normalize to { type: "object", properties: {} }, custom configured Computer Use server names remain supported, pending approval elicitations keep the turn request active until the bridge resolves, non-form elicitations remain unhandled, the app-server bridge tests cover those cases, and Slack docs list /approve.
• What did NOT change (scope boundary): No native Slack UI behavior, gateway approval transport, broad server-name fragment matching, or non-Computer Use plugin approval policy is changed.

Motivation

• This preserves the cherry-picked bridge elicitation fix on top of current main while keeping the existing configured-server authorization boundary intact and preserving the manual approval request lifetime.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #
• Related #
• This PR fixes a bug or regression

Real behavior proof (required for external PRs)

• Behavior or issue addressed: configured Computer Use app-server MCP form elicitations are routed into plugin approvals even when the elicitation request does not include an object schema, and the app-server request activity remains active until the approval bridge resolves.
• Real environment tested: Local OpenClaw Codex worktree unit/seam tests.
• Exact steps or command run after this patch: node scripts/run-vitest.mjs extensions/codex/src/app-server/run-attempt.test.ts extensions/codex/src/app-server/elicitation-bridge.test.ts; git diff --check.
• Evidence after fix (screenshot, recording, terminal capture, console output, redacted runtime log, linked artifact, or copied live output): Test Files 2 passed (2); Tests 230 passed (230) and git diff --check exited cleanly.
• Observed result after fix: The focused app-server bridge suites pass with configured Computer Use elicitations bridged through plugin approval handling, including schema-less elicitations, custom configured server names, and pending approval request lifetime tracking.
• What was not tested: Live Slack plus Computer Use roundtrip was not rerun in this cherry-pick PR.
• Before evidence (optional but encouraged): N/A.

Root Cause (if applicable)

• Root cause: The bridge rejected non-object requestedSchema values before plugin approval handling could accept a valid configured Computer Use form elicitation. Separately, returning the bridge promise from inside a try/finally without await let request-response bookkeeping run before manual approval finished.
• Missing detection / guardrail: Coverage did not lock schema-less Computer Use elicitation requests while preserving exact configured server-name matching, the form-mode guard, and pending request lifetime.
• Contributing context (if known): This change is a current-main cherry-pick of the bridge elicitation fix plus the await fix needed for the async approval bridge callsite.

Regression Test Plan (if applicable)

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
• Target test or file: extensions/codex/src/app-server/elicitation-bridge.test.ts; extensions/codex/src/app-server/run-attempt.test.ts.
• Scenario the test should lock in: configured Computer Use form elicitations bridge with missing schemas normalized to an empty object schema, custom configured server names still work, non-form/non-Computer Use elicitations remain unhandled, and the request :response progress marker does not fire until the elicitation bridge promise resolves.
• Why this is the smallest reliable guardrail: The bug is in the app-server bridge decision and request-handler lifetime path, so focused app-server tests exercise the contract without requiring a live channel.
• Existing test that already covers this (if any): Existing bridge tests covered approval roundtrip mapping, but not this schema shape with the configured-server boundary or the async request lifetime.
• If no new test is added, why not: N/A.

User-visible / Behavior Changes

Slack channel docs now list /approve among app commands. Computer Use app-server approval elicitations are more reliably bridged into plugin approval handling when their request schema is omitted or not an object, and pending approval requests are not treated as responded before the approval bridge resolves.

Diagram (if applicable)

Before:
[configured Computer Use form elicitation] -> [non-object schema rejection] -> [falls through]
[pending approval bridge promise] -> [request finally runs early] -> [turn can idle/complete too soon]

After:
[configured Computer Use form elicitation] -> [empty schema normalization] -> [plugin approval bridge]
[pending approval bridge promise] -> [await bridge] -> [request finally runs after approval response]

Security Impact (required)

• New permissions/capabilities? (Yes/No): No
• Secrets/tokens handling changed? (Yes/No): No
• New/changed network calls? (Yes/No): No
• Command/tool execution surface changed? (Yes/No): No
• Data access scope changed? (Yes/No): No
• If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

• OS: macOS
• Runtime/container: Node via scripts/run-vitest.mjs
• Model/provider: N/A
• Integration/channel (if any): Codex app-server / Computer Use MCP elicitation bridge
• Relevant config (redacted): N/A

Steps

1. Run node scripts/run-vitest.mjs extensions/codex/src/app-server/run-attempt.test.ts extensions/codex/src/app-server/elicitation-bridge.test.ts.
2. Run git diff --check.

Expected

• Focused app-server bridge tests pass and the diff has no whitespace errors.

Actual

• Test Files 2 passed (2); Tests 230 passed (230).
• git diff --check exited cleanly.

Evidence

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

• Verified scenarios: Focused app-server bridge tests for configured Computer Use elicitation routing, run-attempt delegation, and pending elicitation request lifetime.
• Edge cases checked: Missing or non-object Computer Use schema normalizes to an empty object schema; custom configured desktop-control server names work; non-form elicitations remain unhandled; non-Computer Use server names remain unhandled by the Computer Use bridge; request response progress is emitted only after the bridge promise resolves.
• What you did not verify: Live Slack plus Computer Use roundtrip for this branch.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

• Backward compatible? (Yes/No): Yes
• Config/env changes? (Yes/No): No
• Migration needed? (Yes/No): No
• If yes, exact upgrade steps: N/A

Risks and Mitigations

• Risk: accepting a missing or non-object schema for configured Computer Use elicitations relaxes schema validation for this bridge path.
  • Mitigation: the exact configured MCP server-name check and mode: "form" guard remain in place, the normalized response schema has no fields, and focused tests cover custom configured servers plus non-form rejection.
• Risk: awaiting the bridge can keep the app-server request open while manual approval is pending.
  • Mitigation: this is the intended request lifetime; the existing run abort signal and turn idle controls still bound the attempt, and focused coverage verifies response bookkeeping waits for bridge completion.