tools disable

[kingWYZ]

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

I want to delete or disable this web scraping tool. What should I do? Can I operate the page directly? My version is 1.13.0.

[dosubot[bot]]

There's no UI option to disable built-in tools like web scraping directly from the page. However, you can disable it using the POSITION_TOOL_EXCLUDES environment variable.

Add this to your environment configuration (e.g., .env file) and restart the server:

POSITION_TOOL_EXCLUDES=webscraper

To exclude multiple tools, use a comma-separated list:

POSITION_TOOL_EXCLUDES=webscraper,other_tool

This is a global setting that affects all workspaces [1] [2].

Note: Since the web scraping tool doesn't require credentials, environment variables are currently the only way to hide it — there's no admin panel toggle for credential-free built-in tools.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[kingWYZ]

I am using Docker for deployment. I modified the value of POSITION_TOOL_EXCLUDES in the .env file under the Docker path, and then restarted the API and worker containers. Why can it still be found?

[dosubot[bot]]

A few things to check:

1. Correct .env file location — In a Docker Compose deployment, Dify loads environment from multiple files. The .env at the root of the Docker directory is loaded last as an override [1]. Make sure you're editing that file and not a different one (e.g., ./envs/core-services/shared.env also defines this variable) [2].

2. Verify the exact value — The identifier must be exactly webscraper (no underscore, no spaces) [3]:

   POSITION_TOOL_EXCLUDES=webscraper
   

3. Recreate the containers, not just restart — With Docker Compose, a restart doesn't always pick up .env file changes. Try:

   docker compose down
   docker compose up -d

   A docker compose restart reuses the existing container environment, while down + up forces Docker Compose to re-read the .env file and recreate the containers with the updated variables.

4. Verify the variable reached the container — You can confirm with:

   docker compose exec api env | grep POSITION_TOOL_EXCLUDES

The most common cause of this issue is using restart instead of down/up, since restart doesn't re-read environment files.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[kingWYZ]

Where is the .env file located in the container? I want to directly modify the configuration file inside the container, without recreating the container.

[dosubot[bot]]

There is no .env file inside the container — the Dockerfile doesn't copy one into the image [1]. Environment variables are injected by Docker Compose at container creation time from the host's .env files [2], and they become immutable once the container is running.

So unfortunately, you cannot change POSITION_TOOL_EXCLUDES without recreating the container. There's no file to edit inside.

However, recreating doesn't mean losing data — your volumes are preserved. The simplest approach:

# Edit .env on your Docker host first, then:
docker compose up -d --force-recreate api worker

This recreates only the api and worker containers with the new environment, without touching your database or other services. It's fast and non-destructive.

Alternatively, you can set the variable directly on the running container's process as a quick test (though it won't persist across restarts):

docker compose exec api sh -c 'export POSITION_TOOL_EXCLUDES=webscraper && ...'

But this won't work either since the application reads its config at startup. The up --force-recreate approach is really the way to go here.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.