Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [MutliAgent] lost previous tools result in prompt when ToolExpert call tools repeatedly #2136

Closed
3 of 15 tasks
cinjoseph opened this issue Nov 19, 2024 · 0 comments · Fixed by #2137
Closed
3 of 15 tasks
Labels
bug Something isn't working Waiting for reply

Comments

@cinjoseph
Copy link
Contributor

Search before asking

  • I had searched in the issues and found no similar issues.

Operating system information

MacOS(M1, M2...)

Python version information

=3.11

DB-GPT version

latest release

Related scenes

  • Chat Data
  • Chat Excel
  • Chat DB
  • Chat Knowledge
  • Model Management
  • Dashboard
  • Plugins

Installation Information

Device information

macos

Models information

qwen-trubo

What happened

When using MultiAgent, the Planner devises a plan to accomplish an action by utilizing two tools. The first tool is invoked successfully and returns the correct result. However, the execution of the second tool relies on the result from the first tool. During the second tool invocation, the result from the first tool was not stored in memory, causing the second tool to fail to execute successfully.

human: 最近消息记录:
Question: 使用get_current_system_time工具获取当前时间戳 
Thought: {
  "thought": "用户希望使用get_current_system_time工具来获取当前的时间戳,该工具不需要任何参数。",
  "tool_name": "get_current_system_time",
  "args": {}
} 
用户输入: Read the result data of the dependent steps in the above historical message to complete the current goal:使用format_time_stamp工具将时间戳转换为'yy-mm-dd'格式

What you expected to happen

write the result into memory

How to reproduce

may lost observation in template in some commit, add it bak is ok

Additional context

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Waiting for reply
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants