How to enable Agentic Strategy feature on Agent with docker self host version

[pdt590]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

Anyone know how to enable Agentic Strategy feature on Agent with docker self host version?
Thank you

• Self host

- Cloud

[dosubot[bot]]

The "Agentic Strategy" feature you see on Dify Cloud but not on your self-hosted instance is part of the Agent V2 functionality, which is disabled by default on self-hosted Docker deployments. There is no separate feature flag just for the strategy selector — it depends on enabling Agent V2 and having the right plugins installed.

To enable it, add these two environment variables to your docker/.env file [1]:

ENABLE_AGENT_V2=true
NEXT_PUBLIC_ENABLE_AGENT_V2=true

Then restart your containers:

docker compose up -d

After enabling, you should see the Agent Roster page in the navigation where you can create Agent V2 instances with the Agentic Strategy options.

A few additional things to verify:

• Use Dify 1.16.0+ — earlier versions (like 1.15.0) didn't include the agent_backend service in Docker Compose by default, which caused runtime errors [2].
• Plugin Daemon must be running — agent strategies are implemented as plugins, so the available strategies depend on which agent-strategy plugins are installed and whether the Plugin Daemon service is reachable [3].
• Install agent-strategy plugins — the strategies that appear in the dropdown are determined by installed plugins, not a feature flag. Cloud may have more plugins pre-installed than your self-hosted instance.

What version of Dify are you running? That would help narrow down if there are additional steps needed for your setup.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[dosubot[bot]]

Thanks for clarifying! I can see from your original screenshots that you're comparing the legacy Agent app (created from the Studio/Apps page) on self-hosted vs. Cloud. Here's the key issue:

"Agentic Strategy" is only available in Agent V2, not in the legacy Agent app. These are two separate systems in Dify [1]:

• Legacy Agent app (what you're using, created from Studio → "Agent" app type): Only shows "Agent Mode" with Function Calling / ReAct strategies [2]. This is the same on both Cloud and self-hosted.
• Agent V2 (created from the Agent Roster page at /roster): Shows "Agentic Strategy" with plugin-based strategies [3] [4]. This is what Dify Cloud screenshots show.

To access the Agentic Strategy feature on your self-hosted 1.16.1 instance:

1. Ensure Agent V2 is enabled — add these to your docker/.env if not already present [5]:

   ENABLE_AGENT_V2=true
   NEXT_PUBLIC_ENABLE_AGENT_V2=true

2. Restart containers: docker compose up -d

3. Navigate to the Agent Roster page — look for "Agents" in your left sidebar navigation (route: /roster). Create your agent from there instead of from the Studio/Apps page.

4. Verify agent_backend is running: docker compose ps — you should see the agent_backend service up [6].

The Agentic Strategy dropdown will appear when you create/edit agents through the Agent Roster, not through the legacy Studio Agent app type.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[pdt590]

# Step 1: Check env
docker compose exec agent_backend env 
# Result:
ENABLE_AGENT_V2=true
NEXT_PUBLIC_ENABLE_AGENT_V2=true

# Step 2: Check agent_backend
docker compose ps
# Result
agent_backend

Still there is not Agentic Strategy feature @dosu

[dosubot[bot]]

I think there are two things to check here:

1. Verify the env var is set in the web container, not just agent_backend

You checked NEXT_PUBLIC_ENABLE_AGENT_V2 inside the agent_backend container, but this is a frontend variable — it needs to be available in the web container to control the UI [1]. Please verify:

docker compose exec web env | grep NEXT_PUBLIC_ENABLE_AGENT_V2

If it's not set there, make sure NEXT_PUBLIC_ENABLE_AGENT_V2=true is in your docker/.env file (which the web service reads via env_file) [2], then restart:

docker compose up -d

2. Look for "Agents" in the left sidebar — it's a separate page

The Agentic Strategy feature is not in the legacy Agent app you create from Studio. It's on the Agent Roster page, which appears as a separate "Agents" menu item in the left sidebar at route /agents [3] [4]. After the env var is properly set in the web container, you should see this menu item appear.

If the env var is confirmed in the web container but the menu still doesn't show, also check that your user account has the canManageAgents permission [3].

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[pdt590]

1. Check result: NEXT_PUBLIC_ENABLE_AGENT_V2 = true

2. There is Agents menu item in the left sidebar 3. Go inside an agent. Still there is not Agentic Strategy feature @dosu

[dosubot[bot]]

Thanks for the screenshots — that clears things up. I need to correct my earlier guidance.

The "Agentic Strategy" selector is not part of the Agent Roster agent configuration page. The Agent Roster page (/agents) creates standalone agents that currently use a fixed function-calling strategy internally, without exposing a strategy selector in the UI [1].

The "Agentic Strategy" selector appears in Workflow/Chatflow Agent nodes instead [2]. To use it:

1. Create a Chatflow or Workflow app (from Studio)
2. Add an Agent node to your flow
3. You'll see the Agentic Strategy dropdown in that node's configuration panel

Additionally, since you're on a self-hosted instance, you'll need to install agent strategy plugins first — Dify Cloud has these pre-installed, but self-hosted deployments require manual installation [3]:

• Go to the Plugins page in your Dify instance
• Search for and install agent strategy plugins (from the marketplace, GitHub, or local packages)

Without strategy plugins installed, the selector will appear but show an empty list.

Sorry for the runaround — the "Agentic Strategy" feature lives in Workflow/Chatflow Agent nodes, not in standalone agents from the Roster page.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[pdt590]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

Anyone know how to enable Agentic Strategy feature on Agent with docker self host version? Thank you

• Self host

- Cloud

@dosu: Check my first picture. There is not the "Agentic Strategy" feature lives in Workflow Agent node

[dosubot[bot]]

Thank you for the screenshots — now I can see exactly what's happening. I can see the difference clearly:

• Your self-hosted screenshot shows the Agent V2 node (with "Inline setup", "Agent Task", "Output Variables") [1]
• The Cloud screenshot shows the Agent V1 node (with "Agentic Strategy" dropdown, "Model", "Tool List", "Instruction") [2]

These are actually two completely different Agent node implementations in the workflow editor [3]:

• Agent V1 node → Has the "Agentic Strategy" selector (plugin-based strategies like FunctionCalling)
• Agent V2 node → Has "Inline setup" / roster agent binding (no strategy selector — strategy is handled internally)

Since you have ENABLE_AGENT_V2=true, your instance is creating the newer Agent V2 nodes in workflows, which use a different approach — the strategy is managed internally rather than through a user-facing dropdown. The Cloud screenshot appears to be using the older Agent V1 node which exposes the strategy selector.

These are two different design philosophies — Agent V2 nodes handle strategy selection internally and focus on task-based configuration instead, while Agent V1 nodes let you explicitly pick a strategy plugin.

If you specifically need the Agent V1 node with the "Agentic Strategy" dropdown in your workflows, you could try setting ENABLE_AGENT_V2=false and NEXT_PUBLIC_ENABLE_AGENT_V2=false and restarting — this should give you the legacy Agent node with the strategy selector. However, you'd lose the Agent Roster and V2 features.

That said, this could also be a version difference in what Dify Cloud is currently running vs your 1.16.1 instance. Can you confirm whether the Cloud screenshot was taken recently, or from an earlier version?

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.