add exports of AgentTool, AgentTools in index.ts #312
Merged
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.
Issue Link #311
Fixes #311
Summary
Changes
This PR adds missing exports for
AgentTool
andAgentTools
from the TypeScript SDK. While the documentation describes how to useAgentTool
for adding custom tools to aSupervisorAgent
, the package'sindex.ts
file does not exportAgentTool
, making it inaccessible to users importing from the SDK directly.This change ensures that developers can now follow the documented examples without encountering missing export errors.
User experience
Before:
Users trying to use
AgentTool
(as per the documentation) would encounter errors due to it not being exported from the SDK.After:
AgentTool
is now correctly exported, allowing users to implement custom tools in their multi-agent workflows as shown in the documentation.Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.