What
The homeboy-cli / homeboy-codebox-agent-tasks guidance blocks in wp-coding-agents-agents-md.php render ~2,028 bytes of WP Codebox detail into the ## Homeboy section of the composed AGENTS.md. WP Codebox already registers its own ## WP Codebox section (3,082 bytes) covering the same surface.
Measured on extrachill.com, wp-coding-agents 1.22.2:
| Section |
Bytes |
| Codebox total (2,028 nested in Homeboy + 3,082 standalone) |
5,110 |
| Data Machine |
2,711 |
| Extra Chill CLI |
2,218 |
Codebox documentation is 2.3× the Extra Chill CLI, the platform's primary command surface.
The duplicated paragraphs inside ## Homeboy (composed AGENTS.md lines 88–96):
- Codebox executor — sandbox recipes, plugin/runtime overlays, artifact bundles
- WP Codebox agent mode — sandbox mode tooling
- Codex provider —
AI_PROVIDER_OPENAI_CODEX_* secret_env wiring
- Claude Code provider — full OAuth credential paragraph (
AI_PROVIDER_CLAUDE_CODE_REFRESH_TOKEN / _ACCESS_TOKEN / _EXPIRES_AT)
Why it matters
- Layering. Homeboy is the orchestration layer; it is documenting the provider credential surface of a layer below it. Provider secret names belong to whoever owns the provider. Homeboy should know "codebox is an executor backend" and nothing more.
- Context cost. This is always-on context on every agent turn, on every install that has both.
- Drift risk. Two owners documenting one surface diverge silently. The Codebox section is already incomplete — it omits
run-fuzz-suite, run-runtime-package, wordpress-fuzz-runtime-contract, and artifacts get, all of which exist live.
Proposed
In the Homeboy section, keep a one-line pointer — "Codebox is an executor backend; see the WP Codebox section" — and drop the four provider paragraphs. Let wp-codebox own its own documentation.
Not a correctness bug
Every command the section documents was verified against live --help on this install and all exist: homeboy agent-task controller, homeboy agent-task fanout cook-batch, homeboy agent-task submit|run|run-plan|status|logs|artifacts|promote, wp codebox artifacts preflight-apply|stage-apply|apply. The content is accurate and current. This issue is purely about duplication and ownership, not staleness.
What
The
homeboy-cli/homeboy-codebox-agent-tasksguidance blocks inwp-coding-agents-agents-md.phprender ~2,028 bytes of WP Codebox detail into the## Homeboysection of the composedAGENTS.md. WP Codebox already registers its own## WP Codeboxsection (3,082 bytes) covering the same surface.Measured on extrachill.com, wp-coding-agents 1.22.2:
Codebox documentation is 2.3× the Extra Chill CLI, the platform's primary command surface.
The duplicated paragraphs inside
## Homeboy(composedAGENTS.mdlines 88–96):AI_PROVIDER_OPENAI_CODEX_*secret_envwiringAI_PROVIDER_CLAUDE_CODE_REFRESH_TOKEN/_ACCESS_TOKEN/_EXPIRES_AT)Why it matters
run-fuzz-suite,run-runtime-package,wordpress-fuzz-runtime-contract, andartifacts get, all of which exist live.Proposed
In the Homeboy section, keep a one-line pointer — "Codebox is an executor backend; see the WP Codebox section" — and drop the four provider paragraphs. Let
wp-codeboxown its own documentation.Not a correctness bug
Every command the section documents was verified against live
--helpon this install and all exist:homeboy agent-task controller,homeboy agent-task fanout cook-batch,homeboy agent-task submit|run|run-plan|status|logs|artifacts|promote,wp codebox artifacts preflight-apply|stage-apply|apply. The content is accurate and current. This issue is purely about duplication and ownership, not staleness.