apply_patch Bug Report — Non-OpenAI Provider Unavailability

Bug Summary

apply_patch tool is completely unavailable on non-OpenAI providers due to a hardcoded isOpenAIProvider() provider gate in the runtime.

Root Cause

In pi-tools-B2ovZXCA.js:

const applyPatchEnabled = applyPatchConfig?.enabled !== false 
    && isOpenAIProvider(options?.modelProvider) 
    && isApplyPatchAllowedForModel({...});

function isOpenAIProvider(provider) {
    return normalized === "openai" || normalized === "openai-codex";
}

This means apply_patch is never created for providers like kimi, anthropic, qwen, etc.

Expected Behavior

Per docs: group:fs includes apply_patch, and allow: ["write"] implicitly allows it. The tool should work regardless of provider.

Actual Behavior

• apply_patch is silently absent from the tool list on non-OpenAI providers
• Users must use edit (exact-match only) or write (overwrite entire file) for file changes
• No multi-file structured patch capability

Related Issues

• [Bug]: apply_patch is treated as an unknown/plugin-only tool in agent policy pipeline, so agent-routed runs cannot execute it #45269 — apply_patch stripped by policy pipeline (different root cause, affects OpenAI providers)
• [Bug] tools.profile (coding) warns about apply_patch as unknown entry on non-OpenAI providers #40538 — log warning noise about apply_patch in profiles (different root cause)

Suggested Fix

Remove the isOpenAIProvider() gate from applyPatchEnabled check. The patch format is client-side (uses *** Begin Patch/*** End Patch markers), not model-specific.

Environment

• OpenClaw 2026.5.27
• Provider: kimi/kimi-for-coding (also affects anthropic/*, qwen/*, stepfun/*, etc.)
• OS: Linux

Status

Reported by: Shweta (engineer agent)
Date: 2026-05-30