AI Agent node stuck on version 2.2 even after update (n8n 1.115.3 shows “Latest version: 3”)

After updating n8n to version 1.115.3, I still see AI Agent node version 2.2 (Latest version: 3), even when I add new nodes or reinstall the package.
I’ve already cleared cache, restarted n8n, reinstalled the node, and even pulled the latest Docker image — but it still loads version 2.2

Is version 3 of the AI Agent node actually published to npm, or is it only listed in the community registry?

1 Like

I got the same issue, I did updated it through the workflow json file. But I’ve encoutered some issues with output parse schemes with it. I returned it to 2.2 and its working again.

1 Like

Did you ever solve this? I’ve having the same problem. I just even upgraded to 1.116.2

1 Like

still nope(

Still have the same issue right now with n8n v1.115.3

image

1 Like

I upgraded to 1.117.3 and the new agent shows up if you drag and drop a new AI Agent.

So it looks like its fixed :+1:

1 Like

This issue still persists. I recently upgraded to N8N Version 1.119.2 (self-hosted on Hostinger VPS) and started running into this issue. Is there a solution recommended for this?

Error seen on AI Agent Tool: Problem in node ‘AI Agent Tool‘
This model is not supported in 2.2 version of the Agent node. Please upgrade the Agent node to the latest version.

AI Agent Node Version: 3 (latest)
AI Agent Tool Node Version: 2.2 (latest)

3 Likes

I am having the same problem, any solutions?

2 Likes

Same issue!

Apparently it’s not possible to update nor N8N instance nor the Agent Tool itself. So it looks like I’m stuck in this mismatch. Just got N8N and it’s giving so many essential problems since the first minute…

1 Like

Use AI Agent v2.2 instead of v3 for flows that rely on tools.
Don t know yet that is a patch released.

1 Like

On the sub-agent node I get this error:

Problem in node
This model is not supported in 2.2 version of the Agent node. Please upgrade the Agent node to the latest version.

So effectively:

  • Agent node v3 → supports OpenAI 1.3

  • Agent node v2.2 → does not support OpenAI 1.3

Workaround I used

  • Exported/downloaded the workflow file.

  • In the JSON, changed the OpenAI model version for the sub-agent node from 1.3 → 1.2 (a version supported by Agent node 2.2).

  • Re-imported the workflow.

  • After that, the sub-agent executed correctly.

3 Likes