Repository navigation
fix: Docker networks on 198.18.0.0/15 or 2001:db8::/32 count as private; CLI agent-key cache is best-effort - #488
Merged
Merged
Conversation
…te, and the CLI no longer fails when it cannot cache an agent key A provider on a Docker network using the benchmarking pool (RFC 2544) or the IPv6 documentation range (RFC 3849) was rejected as a public http:// host, so a simulator such as http://wwz-openai:8000/v1 could not be registered. Inside the read-only container, `thinker agent create` failed after creating the agent because the local key cache could not be written; the cache is now best-effort. Co-Authored-By: Claude Opus 5.5 <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
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.
Shipped by scripts/ship.sh as v0.31.4.