Reuse extracted ConditionAgent response content when parsing JSON output

[jslim-23]

Feature Description

Reuse a helper extractResponseContent() prior to ConditionAgent response content parsing

Feature Category

Reusability enhancement

Proposed Solution

Reuse the existing extractResponseContent() helper before parsing so that ConditionAgent consistently works with extracted string content.

Since the same value is also used at lines 399 and 473, assign this value to a variable earlier and reuse it.

Mockups or References

• ConditionAgent parsing path: (ConditionAgent.ts#L413)

[HenryHengZJ]

from the UI how do you

Use a LangChain v1 setup where response.content may be serialized as standard content blocks instead of a plain string. ?

[HenryHengZJ]

is this an AI generated issue and then opened its own PR?

[jslim-23]

is this an AI generated issue and then opened its own PR?

Yes, my review agent flagged this as a potential compatibility issue, so I verified it before posting this issue and PR #6072 . I hadn't experienced this from the UI directly.

[jslim-23]

@HenryHengZJ While making this change, I noticed a few nearby spots that were calling extractResponseContent(response.content) in the same way, so I made a small follow-up cleanup to reuse a local variable and reduce some duplication.

[HenryHengZJ]

so how do you replicate this step by step?

[jslim-23]

so how do you replicate this step by step?

You're right to call that out. I overstated this as a reproducible UI bug, and I don't currently have a confirmed step-by-step UI-reproduction.
So the more accurate description on this would be reusing an existent helper, not a confirmed UI-reproduced bug. I'll update the wording in the issue and PR to reflect that.
I apologize for describing this as a bug without validating it properly from the UI side @HenryHengZJ .

[HenryHengZJ]

no worries! so its just a refractor instead of a bug right?

[jslim-23]

no worries! so its just a refractor instead of a bug right?

yes :)