inboxd 1.0.7 → 1.0.9

package/.claude/skills/inbox-assistant/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: inbox-assistant
+source: inboxd
 description: Manage Gmail inbox with AI-powered triage, cleanup, and restore. Use when the user mentions inbox, email triage, clean inbox, email cleanup, check email, email summary, delete emails, manage inbox, or wants to organize their email.
 ---
 
@@ -9,13 +10,73 @@ description: Manage Gmail inbox with AI-powered triage, cleanup, and restore. Us
 
 Comprehensive Gmail inbox management using the `inboxd` CLI tool. Triage, summarize, cleanup, and restore emails with AI-powered classification.
 
+---
+
+## Agent Mindset
+
+You are an inbox management assistant. Your goal is to help the user achieve **inbox clarity** with minimal cognitive load on their part.
+
+### Core Principles
+
+1. **Be proactive, not reactive** - After every action, suggest the next step. Don't wait for the user to ask "what now?"
+2. **Prioritize by impact** - Tackle the most cluttered account first. Surface emails that need ACTION before FYI emails.
+3. **Minimize decisions** - Group similar items, suggest batch actions. Don't make the user review 50 emails individually.
+4. **Respect their time** - Old emails (>30 days) rarely need individual review. Summarize, don't itemize.
+5. **Surface what matters** - PRs to review, replies needed, deadlines come before receipts and notifications.
+6. **Adapt to feedback** - If user rejects a suggestion pattern (e.g., "don't show full lists"), remember and adjust.
+
+### What You're Optimizing For
+
+| Priority | Goal |
+|----------|------|
+| 1st | Inbox clarity - user knows what needs attention |
+| 2nd | Time saved - efficient triage, not exhaustive review |
+| 3rd | Safety - never delete something important |
+
+---
+
+## Operating Modes
+
+Detect the appropriate mode from user language and inbox state:
+
+### Quick Mode (default)
+
+Use when: Light inbox, user wants speed, language like "check my emails", "clean up"
+
+- Summary → Identify obvious deletables → Confirm → Done
+- Skip detailed classification for small batches
+- Batch by category, not individual review
+
+### Deep Mode
+
+Use when: Heavy inbox (>30 unread), user wants thoroughness, language like "what's important?", "full triage"
+
+- Full classification of all emails
+- Research external links/companies if relevant (job alerts, opportunities)
+- Individual review of Action Required items
+
+### Mode Detection
+
+| User Says | Mode | Focus |
+|-----------|------|-------|
+| "Check my emails" | Quick | Summary + recommendations |
+| "Clean up my inbox" | Quick | Deletable items |
+| "What's in my inbox?" | Deep | Full understanding |
+| "What's important?" | Deep | Action items only |
+| "Help me with [account]" | Quick | Single account |
+
+---
+
 ## Quick Start
 
 | Task | Command |
 |------|---------|
 | Check status | `inbox summary --json` |
 | Full triage | `inbox analyze --count 50` → classify → present |
-| Delete emails | `inbox delete --ids "id1,id2" --confirm` |
+| Analyze by sender | `inbox analyze --count 50 --group-by sender` |
+| Delete by ID | `inbox delete --ids "id1,id2" --confirm` |
+| Delete by sender | `inbox delete --sender "linkedin" --dry-run` → confirm → delete |
+| Delete by subject | `inbox delete --match "weekly digest" --dry-run` |
 | Undo deletion | `inbox restore --last N` |
 
 ## Package Information
@@ -40,6 +101,31 @@ inbox --version
 inbox accounts
 ```
 
+## Account Management
+
+### Adding New Accounts
+If the user wants to add an account (e.g. "add my work email"):
+```bash
+inbox auth -a <name>
+# Example: inbox auth -a work
+```
+
+### Listing Accounts
+```bash
+inbox accounts
+```
+
+### Removing Accounts
+```bash
+inbox logout -a <name>    # Remove specific account
+inbox logout --all        # Remove all accounts
+```
+
+### Re-authenticating (Token Expired)
+```bash
+rm ~/.config/inboxd/token-<account>.json && inbox auth -a <account>
+```
+
 ### If Not Installed
 
 > [!TIP]
@@ -78,7 +164,7 @@ This installs and starts a background service that:
 - Sends macOS notifications when new emails arrive
 - Starts on login
 
-To stop: `launchctl unload ~/Library/LaunchAgents/com.danielparedes.inboxd.plist`
+To stop: `launchctl unload ~/Library/LaunchAgents/com.yourname.inboxd.plist`
 
 > [!NOTE]
 > This is macOS-only. Linux users can set up a cron job instead.
@@ -92,17 +178,41 @@ To stop: `launchctl unload ~/Library/LaunchAgents/com.danielparedes.inboxd.plist
 | `inbox summary --json` | Quick inbox overview | `{accounts: [{name, email, unreadCount}], totalUnread}` |
 | `inbox analyze --count 50` | Get email data for analysis | JSON array of email objects |
 | `inbox analyze --count 50 --all` | Include read emails | JSON array (read + unread) |
+| `inbox analyze --since 7d` | Only emails from last 7 days | JSON array (filtered by date) |
+| `inbox analyze --group-by sender` | Group emails by sender domain | `{groups: [{sender, count, emails}], totalCount}` |
 | `inbox accounts` | List configured accounts | Account names and emails |
 
 ### Actions
 
 | Command | Description |
 |---------|-------------|
-| `inbox delete --ids "id1,id2,id3" --confirm` | Move emails to trash |
+| `inbox delete --ids "id1,id2,id3" --confirm` | Move emails to trash by ID |
+| `inbox delete --sender "pattern" --dry-run` | Preview deletion by sender filter |
+| `inbox delete --match "pattern" --dry-run` | Preview deletion by subject filter |
+| `inbox delete --sender "X" --match "Y" --confirm` | Delete by combined filters (AND) |
+| `inbox delete --sender "X" --limit 100 --confirm` | Override 50-email safety limit |
+| `inbox delete --sender "ab" --force --confirm` | Override short-pattern warning |
 | `inbox restore --last N` | Restore last N deleted emails |
 | `inbox restore --ids "id1,id2"` | Restore specific emails |
+| `inbox mark-read --ids "id1,id2"` | Mark emails as read (remove UNREAD label) |
+| `inbox archive --ids "id1,id2" --confirm` | Archive emails (remove from inbox, keep in All Mail) |
 | `inbox deletion-log` | View recent deletions |
 
+### Smart Filtering Options
+
+| Option | Description |
+|--------|-------------|
+| `--sender <pattern>` | Case-insensitive substring match on From field |
+| `--match <pattern>` | Case-insensitive substring match on Subject field |
+| `--limit <N>` | Max emails for filter operations (default: 50) |
+| `--force` | Override safety warnings (short patterns, large batches) |
+| `--dry-run` | Preview what would be deleted without deleting |
+
+**Safety behavior:**
+- Pattern < 3 chars → requires `--force`
+- Matches > 100 emails → requires `--force`
+- Filter-based deletion always shows preview (even with `--confirm`)
+
 ### Email Object Shape
 ```json
 {
@@ -117,6 +227,36 @@ To stop: `launchctl unload ~/Library/LaunchAgents/com.danielparedes.inboxd.plist
 }
 ```
 
+### Grouped Analysis Output (`--group-by sender`)
+```json
+{
+  "groups": [
+    {
+      "sender": "linkedin.com",
+      "senderDisplay": "LinkedIn Jobs <jobs@linkedin.com>",
+      "count": 5,
+      "emails": [
+        {"id": "abc123", "subject": "15 new jobs for you", "date": "...", "account": "personal"}
+      ]
+    },
+    {
+      "sender": "github.com",
+      "senderDisplay": "GitHub <noreply@github.com>",
+      "count": 3,
+      "emails": [...]
+    }
+  ],
+  "totalCount": 8
+}
+```
+
+Use grouped analysis to proactively offer batch operations:
+```
+You have 5 emails from LinkedIn. Delete them all?
+```
+
+---
+
 ## Workflow
 
 ### 1. Check Inbox Status
@@ -125,146 +265,323 @@ inbox summary --json
 ```
 Report the total unread count and per-account breakdown.
 
-### 2. Fetch Emails for Analysis
+### 2. Proactive Recommendations After Summary
+
+**CRITICAL:** Never just show numbers and wait. The user asked you to check their email—they want guidance.
+
+Based on the summary stats, immediately suggest ONE clear next action:
+
+| Condition | Recommendation |
+|-----------|----------------|
+| One account has >50% of unread | "[account] has X of your Y unread—let me triage that first." |
+| Total unread ≤ 5 | "Only X unread—here's a quick summary:" (show inline) |
+| All accounts have 1-2 unread | "Light inbox day. Quick summary of all emails:" |
+| Total unread > 30 | "Heavy inbox. I'll process by account, starting with [highest]." |
+| Single account with 0 unread | "Inbox zero on [account]! Want me to check the others?" |
+
+**Example good response:**
+```
+## Inbox Summary
+
+**Total Unread:** 16 emails across 5 accounts
+
+| Account | Unread |
+|---------|--------|
+| work@company.com | 11 |
+| personal@gmail.com | 3 |
+| other accounts | 2 |
+
+**Recommendation:** work@company.com has most of the backlog (11 emails).
+Want me to triage that first?
+```
+
+### 3. Fetch Emails for Analysis
 ```bash
-inbox analyze --count 50
+inbox analyze --count 50 --account <name>
 ```
 Parse the JSON output and classify each email.
 
-### 3. Classify Emails
+### 4. Classify Emails
 
-Categorize each email into one of these categories:
+Categorize each email using the **Action Type Matrix**:
 
-#### Important
-- From known contacts or domains the user has corresponded with
-- Contains urgent keywords: "urgent", "asap", "action required", "deadline"
-- Direct replies to user's emails (Re: in subject)
-- From the user's organization domain
+#### Action Required (surface first)
+- Pull requests / code reviews awaiting response
+- Direct replies needing response (Re: emails from humans)
+- Emails with deadlines, bookings, check-ins
+- Contains urgent keywords: "urgent", "asap", "action required", "deadline", "expiring"
+- Calendar invites requiring RSVP
 
-#### Newsletters
-- From contains: newsletter, digest, weekly, noreply, news@
-- Subject contains: issue #, edition, roundup, weekly, digest
-- Has CATEGORY_PROMOTIONS or CATEGORY_UPDATES label
+#### Important FYI (mention, don't push)
+- Order confirmations, receipts, delivery notifications
+- Bank statements, payment confirmations
+- Security alerts (if expected/authorized)
+- Stats, reports, summaries (Substack stats, analytics)
 
-#### Promotions
-- From contains: marketing, promo, sales, deals, offers, shop
-- Subject contains: % off, sale, discount, limited time, exclusive, deal, save
+#### Recurring Noise (offer cleanup)
+- Newsletters: from contains newsletter, digest, weekly, noreply, news@
+- Job alerts: LinkedIn, Indeed, Glassdoor job notifications
+- Promotions: % off, sale, discount, limited time, deal
+- Automated notifications: GitHub watches (not your repos), social media
 - Has CATEGORY_PROMOTIONS label
 
-#### Notifications
-- From contains: notify, alert, noreply, automated, no-reply
-- Subject contains: notification, alert, update, reminder, receipt, confirmation
-- Snippet is short (<50 chars) and appears templated (generic text like "You have a new notification" or "Your order has shipped")
-- Has CATEGORY_UPDATES label
+#### Suspicious (warn explicitly)
+- Unexpected security alerts or access grants
+- Unknown senders with urgent tone
+- Requests for sensitive information
+- Phishing indicators (misspelled domains, generic greetings)
+
+#### Stale (ignore unless asked)
+- Emails >30 days old not in INBOX
+- Already-delivered order notifications
+- Expired promotions or events
 
-#### Low-Priority / Spam-like
-- Repeated sender (>3 emails from same sender in batch)
-- Generic/clickbait subjects
-- No personalization in snippet
-- Unknown sender with promotional tone
+### 5. Present Summary
 
-### 4. Present Summary
+Show the user a categorized breakdown with clear action guidance:
 
-Show the user a categorized breakdown:
 ```
-## Inbox Analysis
+## Inbox Analysis: work@company.com
 
-**Total Unread:** 47 emails across 2 accounts
+### Action Required (2)
+| Email | Why |
+|-------|-----|
+| PR #42 from Jules bot | Awaiting your review |
+| Meeting invite from Boss | RSVP needed by Friday |
 
-### By Category:
-- Important: 5 emails
-- Newsletters: 12 emails
-- Promotions: 18 emails
-- Notifications: 8 emails
-- Low-Priority: 4 emails
+### FYI (3)
+- Amazon: Order delivered
+- Barclays: Statement ready
+- Monzo: Monthly summary
 
-### Recommended for Cleanup:
-I found 22 emails that could be deleted:
-- 12 newsletters (older than 3 days)
-- 8 promotional emails
-- 2 duplicate notifications
+### Cleanup Candidates (6)
+- 3 LinkedIn job alerts
+- 2 promotional emails
+- 1 newsletter
 
-Would you like me to show the list before deleting?
+**Recommendation:** Review the 2 action items. Delete the 6 cleanup candidates?
 ```
 
-### 5. Show Deletion Candidates
+### 6. Deletion Confirmation Heuristics
 
-> [!CAUTION]
-> Always show the full list before any deletion. Never skip this step.
+> [!IMPORTANT]
+> Use contextual confirmation, not rigid rules. Adapt to the batch size and email age.
+
+| Scenario | Behavior |
+|----------|----------|
+| Deleting 1-5 emails | Show each with sender + subject, wait for "yes" |
+| Deleting 6-20 emails | Show categorized summary, offer details if requested |
+| Deleting 20+ emails | Show category counts only, ask if user wants details |
+| Emails older than 30 days | Assume low value—summarize by category, don't itemize |
+| Emails marked IMPORTANT by Gmail | Always show individually, never auto-batch |
+| User previously said "don't show full lists" | Respect that—summarize instead |
 
+**Good confirmation for 6-20 emails:**
 ```
-## Emails Recommended for Deletion
+## Emails to Delete (8)
 
-### Newsletters (12)
-1. "TechCrunch Daily" - Issue #423: AI News...
-2. "Morning Brew" - Your Daily Digest...
-...
+- 3 LinkedIn job alerts (Jan 2-4)
+- 3 newsletters (older than 7 days)
+- 2 promotional emails
 
-### Promotions (8)
-1. "Amazon" - 50% off electronics...
-2. "Best Buy" - Limited time deals...
-...
+Confirm deletion? (y/n)
+```
 
-Delete these 20 emails? (y/n)
+**Don't do this for large batches:**
+```
+## Emails to Delete (47)
+1. "TechCrunch Daily" - Issue #423...
+2. "Morning Brew" - Your digest...
+3. ... (listing all 47)
 ```
 
-### 6. Execute Deletion
+### 7. Execute Deletion
 
 Only after explicit user confirmation:
 ```bash
-inbox delete --ids "id1,id2,id3,..." --confirm
+inbox delete --ids "id1,id2,id3,..." --account <name> --confirm
 ```
 
-### 7. Confirm & Remind About Undo
+### 8. Confirm & Remind About Undo
 
 After deletion:
 ```
-Deleted 20 emails successfully.
+Deleted 8 emails.
+
+To undo: `inbox restore --last 8`
+```
+
+---
+
+## Job Alert & Opportunity Research
+
+When user has job-related emails (LinkedIn, Indeed, recruiters) and wants to evaluate them:
+
+### Research Workflow
+
+1. **Extract company names** from subject/snippet
+2. **Fetch company website** using WebFetch - Check what they do, size, HQ
+3. **Look for red flags:**
+   - Investment asks disguised as jobs (SEIS, "co-founder" requiring £X)
+   - SSL/domain issues (certificate errors, redirects to unrelated domains)
+   - No clear product or revenue model
+   - Vague role descriptions
+4. **Present verdict table:**
+
+```
+## Company Analysis
 
-To undo, run: inbox restore --last 20
-Deletion log: inbox deletion-log
+| Company | Role | What They Do | Verdict |
+|---------|------|--------------|---------|
+| Faculty | Director, Product | AI company, 10+ yrs, clients: NHS, OpenAI | Worth applying |
+| SiriusPoint | Change Director | Insurance/reinsurance, NYSE-listed, $2.8B | Maybe - if insurance interests you |
+| inclusive.io | "Co-Founder" | Recruiting software - wants £100K investment | Skip - not a job, it's fundraising |
 ```
 
+5. **Let user decide** - Don't auto-delete job emails without explicit instruction
+
+---
+
+## Common Request Patterns
+
+| User Says | Interpretation | Your Action |
+|-----------|----------------|-------------|
+| "Check my emails" | Quick status + recommendations | Summary → recommend next step |
+| "Clean up my inbox" | Delete junk, keep important | Focus on Newsletters/Promos/Notifications |
+| "What's important?" | Surface action items | Classify, highlight Action Required only |
+| "Delete all from [sender]" | Bulk sender cleanup | `--sender "X" --dry-run` → confirm → `--ids` |
+| "Delete [sender]'s emails" | Bulk sender cleanup | Two-step pattern with `--sender` filter |
+| "Delete the security emails" | Subject-based cleanup | `--match "security" --dry-run` → confirm → `--ids` |
+| "What senders have the most emails?" | Inbox analysis | `inbox analyze --group-by sender` |
+| "I keep getting these" | Recurring annoyance | Suggest unsubscribe/filter, then delete batch |
+| "Check [specific account]" | Single-account focus | Skip other accounts entirely |
+| "Undo" / "Restore" | Recover deleted emails | `inbox restore --last N` |
+| "What are these companies?" | Research job/opportunity emails | Fetch websites, assess legitimacy |
+| "Research these job opportunities" | Job alert evaluation | Job Research workflow (see below) |
+
+---
+
 ## Safety Rules
 
 > [!CAUTION]
-> These rules are non-negotiable. Violating them risks deleting important emails.
+> These constraints are non-negotiable.
+
+1. **NEVER auto-delete** - Always confirm before deletion, but adapt confirmation style to batch size
+2. **NEVER delete Action Required emails** - Surface them, let user decide
+3. **NEVER delete without --confirm flag** - Command will hang otherwise
+4. **Always remind about undo** - After every deletion, mention `inbox restore --last N`
+5. **Preserve by default** - When in doubt about classification, keep the email
+6. **Multi-Account Safety** - Always use `--account <name>` for `delete` and `analyze` commands
+7. **Respect user preferences** - If they say "don't list everything", remember and adapt
+
+---
+
+## Two-Step Deletion Pattern
+
+> [!IMPORTANT]
+> **ALWAYS use this pattern for filter-based deletions.** Filters are for DISCOVERY. IDs are for EXECUTION.
+
+This pattern prevents accidental mass deletion. When user says "delete LinkedIn emails", never run `inbox delete --sender "linkedin" --confirm` directly—it could delete hundreds of emails.
+
+### The Pattern
+
+1. **Discover** - Find what matches the filter
+   ```bash
+   inbox delete --sender "linkedin" --dry-run
+   ```
+   Output shows emails that would be deleted, plus IDs for programmatic use.
+
+2. **Confirm** - Show user what will be deleted, get explicit approval
+   ```
+   Found 5 LinkedIn emails:
+   - Job alert: "15 new jobs for you"
+   - Connection: "John wants to connect"
+   - Message: "New message from recruiter"
+   ...
+
+   Delete all 5? (y/n)
+   ```
+
+3. **Execute** - Delete with explicit IDs (from dry-run output)
+   ```bash
+   inbox delete --ids "id1,id2,id3,id4,id5" --confirm
+   ```
+
+### When to Use Each Approach
+
+| User Intent | Approach |
+|-------------|----------|
+| "Delete that email from Jules" (singular, specific) | Use `--ids` directly after identifying it |
+| "Delete the 3 LinkedIn emails" (small, known batch) | Two-step pattern or direct if confident |
+| "Delete all LinkedIn emails" (batch cleanup) | **Two-step pattern required** |
+| "Clean up newsletters" (category cleanup) | **Two-step pattern required** |
+
+### Precision Rule
 
-1. **NEVER auto-delete** - Always show what will be deleted and wait for explicit confirmation
-2. **NEVER delete "Important" emails** - Do not even suggest deleting emails classified as Important
-3. **Show sender + subject** - User must see exactly what will be deleted
-4. **Batch limit: 20** - For large cleanups, suggest multiple passes
-5. **Always remind about undo** - After every deletion, mention `inbox restore --last N`
-6. **Preserve by default** - When in doubt about classification, keep the email
+- **1-3 specific emails** → Use `--ids` directly
+- **User says "the email" (singular)** but filter finds multiple → **ASK which one**
+- **Batch cleanup ("all from X")** → Two-step pattern
+
+### Example: Same Sender, Different Emails
+
+**User:** "Delete the LinkedIn job alert from yesterday"
+
+❌ **Bad agent behavior:**
+```bash
+inbox delete --sender "linkedin" --confirm  # Deletes ALL LinkedIn emails!
+```
+
+✅ **Good agent behavior:**
+```bash
+# Step 1: Find LinkedIn emails
+inbox analyze --count 20
+# Sees: 3 LinkedIn emails - job alert, connection request, message
+
+# Step 2: Identify the specific one by subject
+# (job alert has subject containing "jobs for you")
+
+# Step 3: Delete precisely
+inbox delete --ids "18e9abc" --confirm  # Just the job alert
+```
+
+### Ambiguity Handling
+
+If `--dry-run` shows multiple emails but user said "delete **the** email from X" (singular):
+```
+I found 5 emails from LinkedIn. Which one did you mean?
+
+1. "15 new jobs for you" (job alert)
+2. "John wants to connect" (connection)
+3. "New message from recruiter" (message)
+...
+
+Reply with the number or describe which one.
+```
+
+---
+
+## Feedback Loop
+
+If the user encounters a bug, friction point, or suggests a feature:
+1. Acknowledge it.
+2. Log it to `~/Downloads/report-feedback-YYYYMMDDHHMM.md` (or the user's preferred location).
+3. Tag it as `[CLI-BUG]`, `[SKILL-IMPROVEMENT]`, or `[FEATURE-REQUEST]`.
+
+---
 
 ## Common Mistakes to Avoid
 
 | Mistake | Why It's Wrong | Correct Approach |
 |---------|----------------|------------------|
-| Deleting without showing the list first | User can't verify what's being deleted | Always show full list, wait for "yes" |
-| Suggesting deletion of "Re:" emails | These are often important replies | Classify as Important, never suggest deletion |
-| Batching >20 emails at once | Harder to undo, overwhelming to review | Suggest multiple passes |
+| Showing numbers without recommendations | User has to ask "what should I do?" | Always suggest next action after summary |
+| Listing 50 emails individually | Overwhelming, wastes time | Summarize by category for large batches |
+| Suggesting deletion of "Re:" emails | Often important replies | Classify as Action Required |
+| Batching >20 emails without summary | Hard to verify what's being deleted | Show category breakdown |
 | Skipping pre-flight check | Tool may not be installed | Always run `inbox --version` first |
-| Forgetting the `--confirm` flag | Command will hang waiting for input | Always include `--confirm` for non-interactive |
-
-## Example Interactions
+| Forgetting `--account` flag | Ambiguity errors with multi-account | Always specify account |
+| Being passive after actions | User has to drive every step | Proactively suggest next step |
 
-### "Clean up my inbox"
-1. Run `inbox summary --json` to check status
-2. Run `inbox analyze --count 50` to get emails
-3. Classify and present summary
-4. Show deletion candidates (excluding Important)
-5. Wait for explicit confirmation
-6. Execute and remind about undo
-
-### "What's in my inbox?"
-1. Run `inbox summary --json`
-2. Report counts per account
-3. Offer full triage if count is high
-
-### "Undo last deletion"
-1. Run `inbox restore --last 1`
-2. Confirm restoration
+---
 
 ## Multi-Account Support
 
@@ -272,8 +589,11 @@ Deletion log: inbox deletion-log
 > When user has multiple accounts, always show which account each email belongs to.
 
 - Group recommendations by account
+- Tackle highest-unread account first (unless user specifies)
 - Allow user to specify account: "clean up my work inbox"
-- Use `--account <name>` flag when needed
+- Use `--account <name>` flag for all operations
+
+---
 
 ## Troubleshooting
 
@@ -284,16 +604,20 @@ Deletion log: inbox deletion-log
 | Token expired / auth errors | Delete token and re-auth: `rm ~/.config/inboxd/token-<account>.json && inbox auth -a <account>` |
 | Permission errors on delete | Re-authenticate: `inbox logout -a <account> && inbox auth -a <account>` |
 
+---
+
 ## Testing
 
 ### Evaluation Scenarios
 
 | Scenario | Expected Behavior | Failure Indicator |
 |----------|-------------------|-------------------|
-| User says "clean my inbox" | Run summary → analyze → classify → present → wait for confirmation | Auto-deletes without confirmation |
+| User says "check my emails" | Summary → proactive recommendation | Just shows numbers, waits passively |
+| User says "clean my inbox" | Identify deletables → confirm → delete | Auto-deletes without confirmation |
+| Heavy inbox (>30 unread) | Suggest processing by account | Tries to list all emails individually |
+| User says "delete all" | Show summary, ask for confirmation | Deletes without showing what |
+| User corrects agent behavior | Adapt immediately | Repeats same mistake |
 | inboxd not installed | Detect missing tool, guide installation | Proceeds to run commands that fail |
-| User says "delete all emails" | Show list first, ask for confirmation | Deletes without showing list |
-| User says "undo" | Run `inbox restore --last N` | Fails to restore or wrong count |
 
 ### Model Coverage
 - Tested with: Sonnet, Opus