Repository navigation
ci: bump Claude Code to 2.1.301, cap usage-limit waits, WebFetch off under egress enforce - #1234
Merged
Merged
Conversation
Pin, npm cache key (aeon.yml + messages.yml), claude adapter rh-meta, regenerated harnesses.json and the README pins.
CLAUDE_CODE_RETRY_WATCHDOG=1 plus CLAUDE_CODE_RETRY_WATCHDOG_MAX_USAGE_LIMIT_WAIT_MS=600000 (2.1.301+) so a run that hits a usage limit resetting far away ends in minutes instead of sitting until the run-harness --timeout guard. Operator values win.
WebFetch runs Anthropic-side and never passes iron-proxy, so in enforce mode set CLAUDE_CODE_DISABLE_WEB_FETCH=1 and it cannot route around the allowlist. Audit mode is unchanged.
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
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.
Bumps the pinned Claude Code from 2.1.287 to 2.1.301 and uses two of its new switches.
Changes
Fixes the fleet gains (2.1.288 to 2.1.301)
Risk: claude -p now waits for background commands (2.1.292)
Before, -p killed a background command 5s after the final result. Now it waits for it. run-harness wraps the adapter in timeout -k 30 1800 (process-group TERM, then KILL), so a skill that leaves a background job running cannot hang the job past 30 min, but it would turn a finished run into a 124 timeout. I found no skill that does this today (fleet-control uses & + wait inside one Bash call). No guard added; if it shows up, the fix is a line in the skill prompt rules or a lower --timeout per skill.
Not touched: aeon-agent and miroshark-aeon pick this up through aeon-update.
Need help on this PR? Tag
@codesmith-botwith what you need.