Replies: 1 comment
|
This appears to be a temporary rollout limitation rather than a permanent design decision. The architecture already supports Agent V2 in both Workflow and Chatflow modes — internal documentation describes Agent V2 as powering Agent nodes in "Workflows and Chatflows" [1]. The restriction you're seeing in 1.16.1 is on the frontend/node palette side, not a backend constraint. Here's what's happening:
Workarounds for now:
That said, there's no public timeline for when Agent V2 with sandbox and skills will be officially available in Chatflow. It does look like this is part of a phased rollout rather than an intentional permanent limitation. To reply, just mention @dosu. Docs are dead. Just use Dosu. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Self Checks
Content
I believe the sandbox environment and skills capabilities are equally necessary for Agent nodes in Chatflow. Why does the current 1.16.1 design keep Chatflow's Agent node unchanged while only enabling sandbox + skills for Workflow's Agent node? Is this a temporary limitation or an intentional design decision?
All reactions