- Newest
- Most votes
- Most comments
You're correct that files uploaded to a Bedrock Supervisor Agent in the console aren't automatically propagated to sub-agents (collaborator agents) in the same way that text prompts are.
This is a known limitation in the current implementation of multi-agent collaboration in Amazon Bedrock. The state sharing between agents, particularly for files and other structured data, doesn't happen automatically.
To share files between agents in a multi-agent setup, you'll need to implement one of these approaches:
-
Have the supervisor agent explicitly pass the necessary file data to each collaborator agent when delegating tasks. This can be done through the conversationHistory field, which is designed for multi-agent collaboration.
-
Ensure that conversationalHistorySharing is enabled for each collaborator agent in your configuration. This allows them to receive context passed by the supervisor agent.
-
When using the API (rather than the console), you can use the sessionState parameter with a "files" field to reference files. For example:
sessionState={
"files": [
{
"name": "your_file.txt",
"source": {
"s3Location": {
"uri": "s3://your-bucket-name/your_file.txt"
},
"sourceType": "S3"
},
"useCase": "CHAT"
}
]
}
- For the supervisor agent, you might need to modify its instructions to explicitly handle file sharing with collaborator agents.
This limitation is part of the current design of Bedrock's multi-agent collaboration system, where state sharing between agents requires explicit handling rather than happening automatically.
Sources
Issue Sharing State Across Agents in Amazon Bedrock | AWS re:Post
Bedrock Agent API Ignores inputFiles Parameter but Console Works | AWS re:Post
Relevant content
asked 2 years ago
asked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 6 months ago
