-
Notifications
You must be signed in to change notification settings - Fork 3.4k
SaveFilesAsArtifactsPlugin: Unexpected Behavior #3663
Copy link
Copy link
Closed
Labels
request clarification[Status] The maintainer need clarification or more information from the author[Status] The maintainer need clarification or more information from the authorstale[Status] Issues which have been marked inactive since there is no user response[Status] Issues which have been marked inactive since there is no user responsetools[Component] This issue is related to tools[Component] This issue is related to tools
Metadata
Metadata
Assignees
Labels
request clarification[Status] The maintainer need clarification or more information from the author[Status] The maintainer need clarification or more information from the authorstale[Status] Issues which have been marked inactive since there is no user response[Status] Issues which have been marked inactive since there is no user responsetools[Component] This issue is related to tools[Component] This issue is related to tools
I have created an agent that is configured with the SaveFilesAsArtifactsPlugin. I intentionally did not configure the load_artifact tool to ensure that the agent cannot use it to load any artifacts. I also configured the GcsArtifactService.
When I upload a file, I can see in the conversation history that everything appears as expected. For example:
However, after the artifact was processed, I noticed a significant delay in each subsequent response from the LLM. From the logs, I found that the input token usage looked like this:
I’m not sure how to interpret that, but it seems that the file’s payload ended up in the context.
To Reproduce
Please share a minimal code and data to reproduce your problem.
Steps to reproduce the behavior:
Expected behavior
The input token usage should be close to the size of your question.
Screenshots
Desktop (please complete the following information):
Model Information: