Fix approval notification toast: placement, coverage, and wording

[DevMando]

What this fixes

The cross-agent "Approval required" notification — the toast that's supposed to appear when an agent you're not currently looking at needs your approval (a file change, a command, a proposed plan) — was unreliable and unclear. Users could miss approvals entirely, or see a broken sliver of the notification. Three related problems, all fixed.

Why it matters

Approvals block an agent until you respond. If the notification doesn't reliably tell you that one is waiting, which agent, and what it wants, agents silently stall and you don't know why. This makes the notification actually dependable.

What was wrong (and what's fixed)

1. The notification was mispositioned

• It appeared only as a thin sliver clipped to the left edge, and became fully visible only when the "Context Snapshots" panel was open — where it overlapped that panel, looking like it belonged to it.
• Cause: it was pinned to the left rail + the (usually-collapsed) Snapshots column instead of the whole window.
• Fixed: it now anchors to the window's top-right and shows correctly on every screen.

2. You got no notification if the agent you had selected needed approval while you were on Settings / MCP / Appearance

• Those screens hide the chat, so you couldn't see the approval — and the toast didn't fire because it only watched other (non-selected) agents.
• Fixed: the toast now fires for any approval you can't currently see (including your selected agent while you're off the chat screen), and it clears when you return. Clicking it takes you straight to that agent's chat.

3. The notification text was unhelpful

• It echoed the approval dialog's question — e.g. "Apply these changes?" or "The assistant proposes this plan. What would you like to do?" — which says nothing about what's actually waiting.
• Fixed: it now shows a specific, at-a-glance summary of the pending action:

Approval	Notification now reads
Proposed plan	Wants to run a proposed plan
Edit a file	Wants to edit <file>
Create a file	Wants to create <file>
Run a command	Wants to run: <command>
Delete	Wants to delete <file>
MCP tool	Wants to run tool "<tool>"

Scope, risk, and testing

• Scope: desktop UI only (notification placement, when it fires, and its text). No change to what actually gets approved or to the agent engine.
• Build: compiles clean (0 warnings, 0 errors).
• Suggested manual check: trigger an approval in a background agent from the chat, Settings, MCP, and Appearance screens; confirm the toast appears top-right, names the right agent, describes the action, and clicking it lands on that agent's chat with the approval visible. Repeat with a proposed plan.

🤖 Generated with Claude Code