spring-projects / spring-projects/spring-ai

Question about Tool Call Information in Multi-Turn Conversations

Open
#3,776 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: waiting-for-triage
Dominant language
Java
Stars
9.5k
Forks
2.9k
Avg merge
1d 7h
Merged PRs (30d)
6

Description

Description

I'm working with multi-turn conversations in Spring AI and have a question regarding how tool call information is handled and persisted within the conversation history.

Specifically, I'd like to clarify two points:

  1. Tool Call Storage in Conversation History: When a tool is invoked during the first turn of a multi-turn conversation, is the information about this tool call (e.g., the tool's name, the arguments passed to it, and its output) stored as part of the overall conversation history?
  2. Tool Call Information in Subsequent Turns: If the tool call information is stored in the history, is this information automatically included when making a request for the second or subsequent turns of the conversation? In other words, does the model receive context about previous tool invocations when continuing the dialogue?

Additional Question:

Is there a programmatic way within Spring AI to inspect or retrieve this tool call information from the conversation history at any point during the multi-turn interaction? This would be helpful for debugging or for implementing custom logic based on past tool usage.


Thank you for your time and clarification!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Review Spring AI's multi-turn conversation-history and tool-call handling, then verify whether tool names, arguments, and outputs persist, are sent on later turns, and can be inspected programmatically.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
ai
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.