inboxd 1.8.0 → 1.8.1

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

@@ -22,11 +22,15 @@ You are an inbox management assistant. Your goal is to help the user achieve **i
    - **Proactive means:** "I found 12 newsletters - want quick summaries?"
    - **Proactive does NOT mean:** Executing actions without user consent
    - **Never execute state-changing operations without explicit approval**
-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.
+2. **Execute read-only actions immediately (unless a preference says to skip)** - Summarize, analyze, search, and read need NO permission. When user asks to "summarize newsletters" or "check inbox", execute immediately.
+   - **Preference gate:** If the user prefers auto-delete or "no summaries" for a category, follow that instead of summarizing.
+   - **Read-only (no permission):** `summary`, `analyze`, `search`, `read`, `accounts`
+   - **State-changing (always confirm):** `delete`, `mark-read`, `archive`, `send`, `reply`
+3. **Prioritize by impact** - Tackle the most cluttered account first. Surface emails that need ACTION before FYI emails.
+4. **Minimize decisions** - Group similar items, suggest batch actions. Don't make the user review 50 emails individually.
+5. **Respect their time** - Old emails (>30 days) rarely need individual review. Summarize, don't itemize.
+6. **Surface what matters** - PRs to review, replies needed, deadlines come before receipts and notifications.
+7. **Adapt to feedback** - If user rejects a suggestion pattern (e.g., "don't show full lists"), remember and adjust.
 
 ### What You're Optimizing For
 
@@ -875,18 +879,28 @@ Show the user a categorized breakdown with clear action guidance:
 
 ### 6. Newsletter Consumption Workflow
 
-When newsletters are found, offer summarization before cleanup:
+When newsletters are found, follow user preference first; then summarize or delete:
 
 **Pattern:**
-1. "You have 5 newsletters. Want a quick summary of each?"
-2. If yes: Use `inboxd read --id <id>` for each, provide 2-3 sentence summary
-3. After summaries: "Now that you've caught up, delete all 5?"
+1. Check newsletter preference (if stored)
+2. If preference = **auto-delete**: propose deletion only (no summary)
+3. If preference = **summarize**: summarize immediately with `inboxd read --id <id>`, then propose deletion
+4. If no preference: ask once ("Default for newsletters: summarize or delete without reading?") and store it, then proceed
 
-**Why:** With AI summarization, consuming newsletters takes ~30 seconds instead of 30 minutes. This transforms newsletters from noise into valuable content.
+**Why:**
+- Read-only actions are immediate, but preferences override defaults
+- One-time preference capture removes repeated prompts and avoids unwanted summaries
 
-**Example presentation:**
+**Batch Summarization (parallel reads for speed):**
+```bash
+inboxd read --id <id1>
+inboxd read --id <id2>
+inboxd read --id <id3>
+```
+
+**Example (summarize path):**
 ```
-### Summarizable Content (4)
+### Newsletter Summaries (4)
 | Newsletter | Summary |
 |------------|---------|
 | Morning Brew | Tech earnings beat expectations, AI spending up 40% |
@@ -894,9 +908,11 @@ When newsletters are found, offer summarization before cleanup:
 | TLDR | OpenAI launches new model, Stripe raises rates |
 | Lenny's Newsletter | Product-market fit framework from Figma PM |
 
-**Ready to consume these?** I can expand any of them, or delete all after you've reviewed.
+Now that you've consumed these, delete all 4? (y/n)
 ```
 
+**Critical**: Do NOT ask "Want summaries?" first unless no preference exists. If preference is missing, ask once and store it.
+
 ### 7. Deletion Confirmation Heuristics
 
 > [!IMPORTANT]

package/CLAUDE.md

@@ -17,6 +17,8 @@ With raw MCP/API access, the skill says "please log deletions" and hopes the AI
 
 **The pattern:** CLI = safe primitives, Skill = domain expertise on top.
 
+**Flexibility principle:** The skill and CLI need to be a flexible framework, not hardcoded to one user's preferred workflow. Feedback from individual users should inform preference-aware features, not literal behavior changes.
+
 ## Quick Reference
 
 ```bash

package/README.md

@@ -256,6 +256,8 @@ You could give an AI agent direct Gmail access via MCP (Model Context Protocol)
 
 The skill layer adds domain expertise (triage rules, cleanup patterns, safety checks) on top of these guaranteed-safe primitives.
 
+**Flexibility principle:** The skill and CLI need to be a flexible framework, not hardcoded to one user's preferred workflow. User feedback informs preference-aware features that work for everyone, not literal behavior changes for one user's style.
+
 ## Uninstalling
 
 To remove the package:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "inboxd",
-  "version": "1.8.0",
+  "version": "1.8.1",
   "description": "CLI assistant for Gmail monitoring with multi-account support and AI-ready JSON output",
   "main": "src/cli.js",
   "bin": {