Problem
A standalone WP Codebox agent-task run can reach the sandbox and invoke the public wp-codebox/run-runtime-package ability, but the run fails before executing the package because the configured default provider dispatches to Agents API's agents/run-runtime-package without any registered wp_agent_runtime_package_run_handler.
Observed normalized error:
agents_runtime_package_run_no_handler: No agents/run-runtime-package handler is registered. Install a consumer runtime or add a callable to the wp_agent_runtime_package_run_handler filter.
Why this matters
wp-codebox/run-runtime-package is exposed as the canonical public WP Codebox runtime-package ability. In the standalone Codebox sandbox, Data Machine is intentionally not present, so the old Data Machine handler path is unavailable. The public Codebox contract should either execute through a Codebox-owned runtime-package provider or fail readiness before dispatching into an unavailable handler.
Evidence shape
- The sandbox loads
agents-api, wp-codebox, and the OpenAI provider plugin successfully.
wp-codebox/run-runtime-package is registered and selected.- The runtime package source is hydrated into an inline package bundle before invocation.
- The provider command exits failed with no file changes and an empty patch.
- The inner runtime error is
agents_runtime_package_run_no_handler.
Expected behavior
Standalone wp-codebox/run-runtime-package should satisfy the Codebox public runtime-package contract without requiring Data Machine. If Agents API remains the canonical dispatcher, WP Codebox should register the required handler or provide a native Codebox runtime-package provider behind WP_Codebox_Runtime_Provider_Registry.
Notes
This blocks the WPSG production loop after the typed-artifact DTO/handoff migration: provider discovery and bundle hydration are now working, but runtime package execution stops at the missing handler boundary.
Problem
A standalone WP Codebox agent-task run can reach the sandbox and invoke the public
wp-codebox/run-runtime-packageability, but the run fails before executing the package because the configured default provider dispatches to Agents API'sagents/run-runtime-packagewithout any registeredwp_agent_runtime_package_run_handler.Observed normalized error:
Why this matters
wp-codebox/run-runtime-packageis exposed as the canonical public WP Codebox runtime-package ability. In the standalone Codebox sandbox, Data Machine is intentionally not present, so the old Data Machine handler path is unavailable. The public Codebox contract should either execute through a Codebox-owned runtime-package provider or fail readiness before dispatching into an unavailable handler.Evidence shape
agents-api,wp-codebox, and the OpenAI provider plugin successfully.wp-codebox/run-runtime-packageis registered and selected.agents_runtime_package_run_no_handler.Expected behavior
Standalone
wp-codebox/run-runtime-packageshould satisfy the Codebox public runtime-package contract without requiring Data Machine. If Agents API remains the canonical dispatcher, WP Codebox should register the required handler or provide a native Codebox runtime-package provider behindWP_Codebox_Runtime_Provider_Registry.Notes
This blocks the WPSG production loop after the typed-artifact DTO/handoff migration: provider discovery and bundle hydration are now working, but runtime package execution stops at the missing handler boundary.