Skip to content

fix(llm-client): handle empty string arguments in Anthropic convertMessages #1879

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.

Sign up for GitHub

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

Closed
GusCayresMindsight wants to merge 1 commit into from
Closed

fix(llm-client): handle empty string arguments in Anthropic convertMessages #1879

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions multimodal/tarko/llm-client/src/handlers/anthropic.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -413,7 +413,8 @@ export const convertMessages = async (
};
currentParams.push(toolResult);
} else if (message.role === 'assistant') {
if (typeof message.content === 'string') {
// Anthropic rejects empty text content blocks; skip when content is "".
if (typeof message.content === 'string' && message.content) {
currentParams.push({
text: message.content,
type: 'text',
Expand All @@ -424,7 +425,9 @@ export const convertMessages = async (
const convertedContent: Array<ToolUseBlockParam> = message.tool_calls.map((toolCall) => {
return {
id: toolCall.id,
input: JSON.parse(toolCall.function.arguments),
// Anthropic streaming emits "" for arguments when the tool input is
// an empty object; JSON.parse("") throws — fall back to "{}".
input: JSON.parse(toolCall.function.arguments || '{}'),
name: toolCall.function.name,
type: 'tool_use',
};
Expand Down