Goal
Build BotFucker into a usable branded app, not just a CLI script.
The UI should make inbox defense feel fast, funny, and slightly hostile to spam bots while staying safe by default.
Branding
Use the existing FF2K/BotFucker hero art and repo visual identity:
- bold dark UI
- orange/blue accent colors from the logo
- anti-bot / inbox-defense vibe
- readable, not gimmicky
- "delete bloat, keep signal" energy
Core screens
1. Dashboard
Show:
- emails scanned
- spam/cold outreach detected
- warnings drafted
- senders on strike 1/2/3
- blocked/blacklisted domains
- pending review count
2. Review queue
For each flagged email:
- sender
- company/domain
- subject
- short LLM/rules summary
- classification
- confidence
- reasons/evidence
- sender history / strike level
- proposed action
- drafted reply
Actions:
- approve reply
- archive
- blacklist sender
- blacklist domain
- whitelist sender/domain
- escalate strike
- mark as safe
3. Sender history
Track each offender:
- first seen / last seen
- number of messages
- warnings sent
- strike level
- domains/company hints
- previous classifications
- current status: review, warned, blocked, whitelisted
4. Settings
Support:
- human approval mode/default
- YOLO mode toggle
- response tone level
- provider connections
- LLM provider/API key settings
- whitelist/blacklist management
YOLO mode
Add an explicit opt-in mode where BotFucker can respond without human approval.
Safety requirements:
- disabled by default
- scary confirmation copy
- separate limits for daily sends
- only allow YOLO for selected classifications/confidence thresholds
- never use most aggressive/legal-ish templates automatically unless explicitly enabled
- full audit log of every action
- easy emergency off switch
Suggested copy:
YOLO mode lets BotFucker reply/block without asking you first. This can save time and also make you look like an unhinged mailbox goblin if configured badly. Start conservative.
Provider auth
Support both managed OAuth and user-supplied keys where appropriate.
Email ingestion options:
- Gmail OAuth
- Microsoft OAuth
- IMAP fallback for developers/self-hosters
- n8n webhook ingestion path
LLM provider options:
- OpenAI API key
- Anthropic API key
- OpenRouter API key
- local/custom endpoint later
Security requirements:
- never commit secrets
- store keys only in local env/secret store/config ignored by git
- document environment variables
- if web app, server-side only; never expose provider keys to browser
Implementation direction
Do not make the UI depend directly on IMAP. Build around internal API/data models:
- normalized email model
- classification result
- sender history
- review action
- draft response
- audit event
The CLI, n8n workflow, and future UI should all share the same core concepts.
Goal
Build BotFucker into a usable branded app, not just a CLI script.
The UI should make inbox defense feel fast, funny, and slightly hostile to spam bots while staying safe by default.
Branding
Use the existing FF2K/BotFucker hero art and repo visual identity:
Core screens
1. Dashboard
Show:
2. Review queue
For each flagged email:
Actions:
3. Sender history
Track each offender:
4. Settings
Support:
YOLO mode
Add an explicit opt-in mode where BotFucker can respond without human approval.
Safety requirements:
Suggested copy:
Provider auth
Support both managed OAuth and user-supplied keys where appropriate.
Email ingestion options:
LLM provider options:
Security requirements:
Implementation direction
Do not make the UI depend directly on IMAP. Build around internal API/data models:
The CLI, n8n workflow, and future UI should all share the same core concepts.