Open
Conversation
Co-Authored-By: Oz <oz-agent@warp.dev>
bnavetta
approved these changes
Apr 13, 2026
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.
i want to let the warp client cli know that it should try to include aws creds for it's agent calls (i.e. using oidc -> sts handshake)
my idea is that "use bedrock for inference" will be an "advanced" run setting in the oz webapp (loom incoming) that will be toggleable if the admin has enabled aws bedrock in the admin panel. we need to plumb this flag thru to the rust client, and i think via flag would work.
i can also see this just being useful for non-oz webapp scenarios too when u want your oz cli to use oidc to just auth itself to bedrock before making AM requests 🤷