fix(vscode): show tool name in permission prompt title

[KeWang0622]

Context

Fixes #8738

The auto-approve permission prompt currently shows only "Permission required" in the title, with no indication of which tool is requesting approval. Users must expand the checkbox section to discover the tool name, which hurts discoverability — especially for MCP tools where the name carries important context (e.g. playwright_click, github_create_issue).

Implementation

Appends the resolved tool label to the permission prompt title via the existing resolveLabel utility:

• Built-in tools get their translated label: "Permission required: Read", "Permission required: Bash"
• MCP tools fall back to the raw tool name: "Permission required: playwright_click"
• Subagent requests also include the label: "Permission required (subagent): Edit"

One-file change, 9 lines added (net +7). No new dependencies, no i18n key changes, no CSS changes.

How to Test

1. bun run extension
2. Trigger any permission prompt (e.g. a file edit, bash command, or MCP tool call)
3. Observe the title now includes the tool name
4. Verify the expanded checkbox section still shows the tool name as before (no regression)

Screenshots

N/A — the change appends text to an existing header string. Before: "Permission required". After: "Permission required: Read".

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 files)

• packages/kilo-vscode/webview-ui/src/components/chat/PermissionDock.tsx

---

_{Reviewed by gpt-5.4-20260305 · 175,783 tokens}

[marius-kilocode]

@KeWang0622 can you show some screenshots? Before after? Thanks

[KeWang0622]

@marius-kilocode Sure! I don't have screenshots of the VS Code extension running, but here's what the change does:

Before: The permission prompt title shows only "Permission required" with no indication of which tool is requesting access.

After: The title shows "Permission required: Read" or "Permission required: playwright_click" — the tool name is appended using the existing resolveLabel utility (which maps internal tool IDs to human-readable names for built-in tools, and passes through the raw name for MCP tools).

The change is 7 net lines in PermissionDock.tsx — it reads tool.toolName from the approval request and appends it to the title via the same resolveLabel function already imported in the file.

Happy to add a screenshot if you can point me to the quickest way to build and run the extension locally — I'll spin it up and capture the before/after.