fix(board-worker): forward CL_ANCHOR to the executor (unblocks agent stages)#347
Merged
Conversation
…fusal) With the baseline blocker fixed (#346), tasks reached the agent stages and the #345 diagnostics surfaced the next failure: the planner stage got a prose refusal 'ContextGuard requires CL_ANCHOR to be set ... run eval $(cl session start ...)' instead of a JSON plan. OC's CLAUDE.md ContextGuard requires every Claude session targeting OC to be anchored; operations-center.sh sets CL_ANCHOR on the fleet, but build_allowlist_env (#340) stripped it (not in _ENV_PASSTHROUGH), re-breaking the #311 unblock — same regression class as the #344 PATH bug. Add CL_ANCHOR/CL_HOME/CL_SESSION_ID to the passthrough (forwarded only when present) so the executor agent stays anchored and cl_dispatch_wrap hydrate/capture is not silently disabled. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Next layer after #346. With baseline validation fixed, tasks reached the agent stages and the #345 diagnostics surfaced the real failure: the planner stage received a prose refusal instead of a JSON plan —
I'm unable to access the codebase because the ContextGuard requires CL_ANCHOR to be set ... run eval $(cl session start <manifest>) first.Root cause
OC's
CLAUDE.mdContextGuard requires every Claude session targeting OC to be anchored.operations-center.shdeliberately setsCL_ANCHORon the fleet, butbuild_allowlist_env(#340) stripped it (not in_ENV_PASSTHROUGH) — so the executor subprocess and the agent it spawns lost it → prose refusal → planner stage fails → run dies. Same regression class as the #344 PATH bug; re-broke the prior #311 CL_ANCHOR unblock.Fix
Add
CL_ANCHOR/CL_HOME/CL_SESSION_IDto the passthrough (forwarded only when present), so the agent stays anchored andcl_dispatch_wraphydrate/capture isn't silently disabled.Verification
CL_ANCHOR forwarded (verified live); 13 env-allowlist tests pass; ruff clean; pre-push audit 0 findings. Deployed directly to the live fleet.