Add extra_headers support to ReActAgent #244
Closed
Conversation
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
eranco74
requested review from
SLR722,
ashwinb,
dineshyv,
dltn,
ehhuang,
hardikjshah,
raghotham,
reluctantfuturist,
vladimirivic and
yanxi0830
as code owners
|
/cc @ashwinb |
…hes--main--changes--next release: 0.1.0-alpha.2
These are the changes we had made on top of whatever Stainless generates. We are going to get them into this repository now so (a) future updates can just be simple PRs from Stainless and (b) we can directly publish from the repository.
Automated Release PR --- ## 0.1.0-alpha.3 (2025-06-27) Full Changelog: [v0.1.0-alpha.2...v0.1.0-alpha.3](llamastack/llama-stack-client-python@v0.1.0-alpha.2...v0.1.0-alpha.3) ### Features * **api:** update via SDK Studio ([e87f225](llamastack@e87f225)) * make custom code changes ([llamastack#3](llamastack#3)) ([83fa371](llamastack@83fa371)) --- This pull request is managed by Stainless's [GitHub App](https://github.com/apps/stainless-app). The [semver version number](https://semver.org/#semantic-versioning-specification-semver) is based on included [commit messages](https://www.conventionalcommits.org/en/v1.0.0/). Alternatively, you can manually set the version number in the title of this pull request. For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request. 🔗 Stainless [website](https://www.stainlessapi.com) 📚 Read the [docs](https://app.stainlessapi.com/docs) 🙋 [Reach out](mailto:support@stainlessapi.com) for help or questions --------- Co-authored-by: stainless-app[bot] <142633134+stainless-app[bot]@users.noreply.github.com>
…tack#5) Stainless by default uses Rye. We need to make it use UV which is more modern (and a significantly upgraded version of Rye.) I have completely nuked existing CI workflows installed by Stainless and instead added our own pre-commit. We will gradually make this more robust by running a lot more tests before landing the client SDK PRs.
Automated Release PR --- ## 0.1.0-alpha.4 (2025-06-27) Full Changelog: [v0.1.0-alpha.3...v0.1.0-alpha.4](llamastack/llama-stack-client-python@v0.1.0-alpha.3...v0.1.0-alpha.4) ### Features * **api:** update via SDK Studio ([4333cb0](llamastack@4333cb0)) ### Bug Fixes * **ci:** update pyproject.toml to use uv and remove broken CI ([llamastack#5](llamastack#5)) ([7bc925c](llamastack@7bc925c)) ### Chores * **internal:** version bump ([867ea24](llamastack@867ea24)) --- This pull request is managed by Stainless's [GitHub App](https://github.com/apps/stainless-app). The [semver version number](https://semver.org/#semantic-versioning-specification-semver) is based on included [commit messages](https://www.conventionalcommits.org/en/v1.0.0/). Alternatively, you can manually set the version number in the title of this pull request. For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request. 🔗 Stainless [website](https://www.stainlessapi.com) 📚 Read the [docs](https://app.stainlessapi.com/docs) 🙋 [Reach out](mailto:support@stainlessapi.com) for help or questions --------- Co-authored-by: stainless-app[bot] <142633134+stainless-app[bot]@users.noreply.github.com>
…ck#8) Supersedes llamastack#251 Signed-off-by: Nathan Weinberg <nweinber@redhat.com>
Fixes this: <img width="1035" alt="image" src="https://github.com/user-attachments/assets/2e43d8c9-2f76-40fb-ab21-abec2f161f95" />
…amastack#11) # What does this PR do? Added the ability to specify the model type when registering models. Also fixed a bug with passing metadata which would result in the following error: ``` Error Type: BadRequestError │ │ Details: Error code: 400 - {'error': {'detail': {'errors': [{'loc': ['body', 'metadata'], 'msg': 'Input should be a valid dictionary', 'type': 'dict_type'}]}}} ``` Closes: llamastack#215 ## Test Plan Run the following commands ``` # Note a Llama Stack Server must be running # Create a venv uv sync --python 3.12 # Install the LSC with the new code changes uv pip install -e . # List the available models llama-stack-client models list # Register the granite-embedding-30m embedding model NOTE must have sentence-transformers as an inference provider llama-stack-client models register granite-embedding-30m --provider-id "sentence-transformers" --provider-model-id ibm-granite/granite-embedding-30m-english --metadata '{"embedding_dimension": 384}' --model-type embedding # Verify the embedding model added are present llama-stack-client models list ```
Fixes broken links to guide to setup a llama-stack server and to the API reference Signed-off-by: Jorge Garcia Oncins <jgarciao@redhat.com>
This is a followup for: add client-side utility for getting OAuth tokens simply llamastack#230 - Add extra_headers parameter to ReActAgent.__init__ method - Pass extra_headers to parent Agent class
eranco74
force-pushed
the
ReActAgentHeaders
branch
from
4a3852c to
64b9f3d
Compare
|
Closed in favor of #14 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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.
What does this PR do?
This is a follow-up for: add client-side utility for getting OAuth tokens simply #230
This PR now enables extra_headers in the ReActAgent