-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Address Crabpot OpenClaw plugin compatibility findings #2845
Copy link
Copy link
Closed
Labels
NV QABugs found by the NVIDIA QA TeamBugs found by the NVIDIA QA TeamUATIssues flagged for User Acceptance Testing.Issues flagged for User Acceptance Testing.VDRLinked to VDR findingLinked to VDR findingintegration: openclawOpenClaw integration behaviorOpenClaw integration behaviorrefactorPR restructures code without intended behavior changePR restructures code without intended behavior change
Metadata
Metadata
Assignees
Labels
NV QABugs found by the NVIDIA QA TeamBugs found by the NVIDIA QA TeamUATIssues flagged for User Acceptance Testing.Issues flagged for User Acceptance Testing.VDRLinked to VDR findingLinked to VDR findingintegration: openclawOpenClaw integration behaviorOpenClaw integration behaviorrefactorPR restructures code without intended behavior changePR restructures code without intended behavior change
Type
Fields
Give feedbackNo fields configured for issues without a type.
Background
OpenClaw's new Crabpot compatibility harness is inspecting NemoClaw as a fixture because this repo contains a native OpenClaw plugin package under
nemoclaw/.NemoClaw is still broader than that plugin: the host CLI and blueprint orchestrate OpenShell, and OpenShell runs/sandboxes OpenClaw. Crabpot is specifically testing the OpenClaw plugin subpackage that registers
/nemoclaw, the managed inference provider, and plugin hooks inside the OpenClaw runtime.Crabpot report context: https://github.com/openclaw/crabpot
NemoClaw-side fixes to track
nemoclaw/package.json, underopenclaw.compat.pluginApior whatever exact current convention OpenClaw confirms.before_agent_startcompatibility and onto the current hook phases, likelybefore_model_resolveand/orbefore_prompt_build, preserving the runtime context injection behavior.Findings that appear to be Crabpot/inspector follow-up, not NemoClaw product fixes
nemoclaw/package.jsonpointsopenclaw.extensionsat./dist/index.js, which is normal for this TypeScript package. Crabpot already models this via isolated workspace install/build before probes.before_tool_callterminal/block/approval probes and runtime registration capture gaps: these are inspector coverage gaps for Crabpot/plugin-inspector, not evidence of a NemoClaw runtime failure.Acceptance criteria
nemoclaw/package.jsondeclares the OpenClaw plugin API compatibility range using the OpenClaw-approved metadata shape and range.before_agent_start, or any remaining compatibility usage is explicitly justified with a removal plan.cd nemoclaw && npm run build && npm testpasses.