Blitz Preferences

Session preferences that control how AI handles emails during blitz sessions. Set once, applied every session.

Purpose

Blitz preferences store persistent settings for how you want email handled: your sign-off style, default tone, noise handling, and delegation rules. The AI checks these before every session.

Mode vs Preferences
The stabilizers/auto mode choice is asked each session and not stored here. These preferences are about how to handle things, not whether to ask first.

Preferences Structure

{
"newsletters": "archive",
"noise_handling": "auto_archive",
"default_tone": "professional",
"sign_off": "Cheers,\nStuart",
"delegation": [
{
"match": "billing|invoice|payment",
"cc_email": "[email protected]",
"reason": "Financial matters"
}
],
"priorities": {
"domains": ["bigclient.com", "investor.co"],
"keywords": ["urgent", "asap", "deadline"],
"senders": []
},
"quick_responses": {
"thanks_acknowledged": "Thanks for this - acknowledged and noted.",
"will_review": "Thanks, I'll review and get back to you shortly.",
"meeting_confirmed": "Confirmed - see you then."
},
"setup_complete": true
}

Field Reference

FieldValuesDescription
newslettersarchive, unsubscribe, askHow to handle newsletter emails
noise_handlingauto_archive, askReceipts, shipping notifications, etc.
default_tonecasual, professional, formalDefault response tone (can be overridden per contact)
sign_offString with \nHow to sign emails (e.g., "Cheers,\nStuart")
delegationArray of rulesWhen to CC others (match pattern, email, reason)
prioritiesObjectDomains, keywords, senders that get high priority
quick_responsesObjectShort phrases for common quick replies
setup_completeBooleanIf false, AI asks setup questions on first run

First Run Setup

If setup_complete is false or the file is empty, the AI will ask:

  1. "When I see newsletters, should I archive them, offer to unsubscribe, or ask you each time?"
  2. "How do you like to sign off emails?"
  3. "Is there anyone I should CC for specific types of issues?"
  4. "For obvious noise (receipts, shipping notifications), should I auto-archive or ask first?"
  5. "What's your default tone? (casual, professional, formal)"

Delegation Rules

Delegation rules tell the AI when to CC someone on responses:

"delegation": [
{
"match": "billing|invoice|payment",
"cc_email": "[email protected]",
"reason": "Financial matters"
},
{
"match": "support|help|issue|bug",
"cc_email": "[email protected]",
"reason": "Customer support"
},
{
"match": "contract|agreement|legal",
"cc_email": "[email protected]",
"reason": "Legal matters"
}
]

The match field is a regex pattern. When an email matches, the AI will suggest (or automatically add in auto mode) the CC.

Quick Responses

Short phrases for common quick replies:

"quick_responses": {
"thanks_acknowledged": "Thanks for this - acknowledged and noted.",
"will_review": "Thanks, I'll review and get back to you shortly.",
"meeting_confirmed": "Confirmed - see you then.",
"received_will_process": "Got it - I'll process this and follow up."
}

You can reference these in sessions: "Send a thanks_acknowledged reply."

Priority Settings

Define what counts as high priority:

"priorities": {
"domains": ["bigclient.com", "investor.co", "partner.io"],
"keywords": ["urgent", "asap", "deadline", "critical"],
"senders": ["[email protected]"]
}

Emails matching these are flagged for immediate attention and never auto-archived.

File Location

~/.config/pontius/knowledge/blitz/preferences.json

How AI Uses Preferences

  1. Check on every blitz session — Load preferences before handling emails
  2. Apply consistently — Use sign_off, tone, delegation rules
  3. Respect noise settings — Don't ask about newsletters if user said auto-archive
  4. Update when directed — If user changes preference mid-session, update the file