chore: add agents repo to allowed_remote_resources#1360
Merged
yashvardhannanavati merged 1 commit intoJul 9, 2026
Merged
Conversation
Adds allowed_remote_resources with both fullsend-ai/fullsend and fullsend-ai/agents URLs. This is required for the agent extraction migration: agent harnesses are now resolved from fullsend-ai/agents at runtime and the URL must be in the allowlist.
yashvardhannanavati
approved these changes
Jul 9, 2026
yashvardhannanavati
merged commit 8dfb4b0
into
release-engineering:master
10 checks passed
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
2 participants
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
allowed_remote_resourceswith bothhttps://raw.githubusercontent.com/fullsend-ai/fullsend/andhttps://raw.githubusercontent.com/fullsend-ai/agents/This change is required before fullsend's
v0tag can move to v0.29.0. The new version resolves agent harnesses fromfullsend-ai/agentsat runtime, and the URL must be in the config allowlist.No behavioral change on the current v0 (v0.28.0).