[Bug]: Custom agents cannot access task tool despite frontmatter configuration

[DevSissi]

Description

Custom agents defined in .opencode/agents/*.md cannot access the task tool even when explicitly configured in frontmatter with tools: { task: allow } and mode: primary or mode: all. The task tool is completely absent from the agent's available tool list.

Steps to Reproduce

1. Create a custom agent file at .opencode/agents/my-agent.md:

---
description: Custom workflow coordinator
mode: primary
model: anthropic/claude-opus-4-6
tools:
  * : allow
  task : allow
---

You are a workflow coordinator that needs to spawn sub-agents.

2. Start OpenCode and switch to the custom agent
3. Try to use the task() tool to spawn a sub-agent
4. The agent reports that the task tool is not available in its tool list

Expected Behavior

Custom agents with tools: { task: allow } in frontmatter should have access to the task tool, allowing them to spawn sub-agents just like built-in primary agents.

Actual Behavior

• The task tool is completely missing from the custom agent's tool list
• The agent cannot spawn sub-agents via task()
• Only built-in primary agents (like Build, Plan) can use the task tool
• Custom agents can see all other tools (bash, read, write, etc.) but not task

Additional Context

Documentation vs Reality

The documentation mentions using permission: for tool configuration:

permission:
  task: allow

However, in the current version (v1.2.6), only the tools: syntax works for opening OpenCode without errors. When using permission:, OpenCode fails to start properly.

Workaround Attempted

Tried various frontmatter configurations:

• mode: primary + tools: { task: allow } ❌
• mode: all + tools: { task: allow } ❌
• mode: subagent + tools: { task: allow } ❌
• permission: { task: allow } ❌ (causes startup failure)

None of these configurations make the task tool available to custom agents.

Environment

• OpenCode version: v1.2.6
• OS: Windows 10 (Git Bash)
• Model: anthropic/claude-opus-4-6

Related Issues

This appears to be related to but distinct from #8114, which addressed nested sub-agents for built-in agents. This issue specifically affects custom agents defined via markdown files, not built-in agents.

Impact

This limitation prevents users from creating custom orchestrator agents that coordinate multiple sub-agents, which is a common pattern for complex workflows. Users are forced to use built-in agents or manually coordinate tasks without delegation.

[github-actions]

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

• Task tool permission override no longer works for nested sub-agents #8114: Task tool permission override no longer works for nested sub-agents — this issue describes the same root problem (task tool cannot be enabled for agents via frontmatter configuration, even with permission: { task: allow }), including the same symptom that only built-in primary agents can use the task tool.

If your issue is distinct from #8114, please add a comment explaining the difference so maintainers can assess it separately.

[OpeOginni]

@DevSissi using this works

---
description: Custom workflow coordinator
mode: primary
model: opencode/glm-5-free
permission:
  task : allow
---

You are a workflow coordinator that needs to spawn sub-agents.

Follows the Docs adding the tool under permission for the Agent.MD the tasks group only works for when adding agents to the json config

[github-actions]

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.