Task tool constantly used even after disabling it. #6775

Open
opened 2026-02-16 18:05:14 -05:00 by yindo · 1 comment
Owner

Originally created by @nitg16 on GitHub (Jan 19, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

I have disabled task tool, but it is constantly called by build agent.

I have following permissions in json settings file.

"permission": {
    "*": "ask",
    "task": "deny",
    "skill": "deny"
  },

When build agent tries to call task tool, i get following output in TUI:

⚙ invalid [tool=task, error=Model tried to call unavailable tool 'task'. Available tools: invalid, question, bash, read, glob, read, glob, grep, edit, write, webfetch, todowrite, todoread, playwright_...] 

This happens frequently and I get tons of such errors and failed tool call requests.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @nitg16 on GitHub (Jan 19, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description I have disabled task tool, but it is constantly called by build agent. I have following permissions in json settings file. ```json "permission": { "*": "ask", "task": "deny", "skill": "deny" }, ``` When build agent tries to call task tool, i get following output in TUI: ``` ⚙ invalid [tool=task, error=Model tried to call unavailable tool 'task'. Available tools: invalid, question, bash, read, glob, read, glob, grep, edit, write, webfetch, todowrite, todoread, playwright_...] ``` This happens frequently and I get tons of such errors and failed tool call requests. ### Plugins _No response_ ### OpenCode version _No response_ ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the bug label 2026-02-16 18:05:14 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 19, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #8114: Task tool permission override no longer works for nested sub-agents - describes issues with task tool permissions being ignored after permission rework
  • #3808: Task should inherit current agent permissions/tools for MCP - discusses how agents can bypass tool restrictions by delegating to sub-agents through the task tool
  • #3756: MCP tool blocking not working - agents can still see and access disabled tools - related to tools not being properly blocked despite configuration

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 19, 2026): This issue might be a duplicate of existing issues. Please check: - #8114: Task tool permission override no longer works for nested sub-agents - describes issues with task tool permissions being ignored after permission rework - #3808: Task should inherit current agent permissions/tools for MCP - discusses how agents can bypass tool restrictions by delegating to sub-agents through the task tool - #3756: MCP tool blocking not working - agents can still see and access disabled tools - related to tools not being properly blocked despite configuration Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6775