ACP: classify Task tool as kind 'think' (subagent cards)

[Seluj78]

Note: This issue was surfaced by the Agent of Empires project (agent-of-empires/agent-of-empires#1904).

Problem

When opencode spawns a subagent via its task tool, the ACP toToolKind function at packages/opencode/src/acp/tool.ts:65-86 returns "other" because "task" falls through to the default branch. This means any ACP client (including the AoE cockpit dashboard) cannot render the task tool call in a dedicated ThinkToolCard — it shows as a generic "other" card instead.

Current code

export function toToolKind(toolName: string): ToolKind {
  const tool = toolName.toLocaleLowerCase()
  switch (tool) {
    case "bash":
    case "shell":  return "execute"
    case "webfetch": return "fetch"
    case "edit":
    case "patch":
    case "write": return "edit"
    case "grep":
    case "glob":
    case "context":
    case "context7_resolve_library_id":
    case "context7_get_library_docs": return "search"
    case "read": return "read"
    default: return "other"
  }
}

Note: "think" is not a recognized ToolKind at all in the current codebase.

Request

Add case "task": return "think" to toToolKind so ACP clients can dispatch task subagent tool calls to the correct card type. This likely also requires adding "think" to the ToolKind type definition.

References

• AoE issue Structured view: aoe-agent subagent Task renders as generic 'other' card, classifyKind misses 'task', no _meta linkage emitted agent-of-empires/agent-of-empires#1904 (blocked by this)
• packages/opencode/src/acp/tool.ts:65-86 — the toToolKind function

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• This appears to be a feature request, but the title does not start with [FEATURE]: as required by the feature request template.
• The feature request template was not used — it requires a verification checkbox confirming you've searched for existing issues and a description of the problem/need in the template format.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[Seluj78]

Yeah no that's wrong. it's a bug and not a feature request.