fix: attach pendingFileMetadata to API conversation stream

This fixes an issue where file metadata from read_file operations was not being
properly attached to the API conversation history stream. The pendingFileMetadata
was being set correctly in the Task object but never incorporated into the
conversation stream, causing subsequent reads of the same file to not recognize
previously read ranges.

The fix modifies addToApiConversationHistory to check for and include any
pending file metadata and tool metadata in the message before adding it to
the conversation stream, ensuring proper tracking of file reads across
multiple operations.

Signed-off-by: Eric Wheeler <[email protected]>

Author: Eric Wheeler

src/core/task/Task.ts

@@ -338,7 +338,24 @@ export class Task extends EventEmitter<ClineEvents> {
 	}
 
 	private async addToApiConversationHistory(message: Anthropic.MessageParam) {
-		const messageWithTs = { ...message, ts: Date.now() }
+		const messageWithTs: ApiMessage = {
+			...message,
+			ts: Date.now(),
+		}
+
+		// Attach pending file metadata and tool metadata if they exist
+		if (this.pendingFileMetadata && this.pendingFileMetadata.length > 0) {
+			messageWithTs.files = this.pendingFileMetadata
+			// Clear pending metadata after attaching it
+			this.pendingFileMetadata = undefined
+		}
+
+		if (this.pendingToolMetadata) {
+			messageWithTs.tool = this.pendingToolMetadata
+			// Clear pending tool metadata after attaching it
+			this.pendingToolMetadata = undefined
+		}
+
 		this.apiConversationHistory.push(messageWithTs)
 		await this.saveApiConversationHistory()
 	}