Research project · Self-hosted · BYOK
Vigil is an open source email agent. Forward emails to it. The agent reads each one, tracks conversation threads, builds persistent memory, and decides what to do — usually nothing. No inbox access. No stored bodies. Bring your own API key.
What it does
Every forwarded email gets analyzed: sender, intent, urgency, entities. The body is discarded after processing. Only a SHA-256 hash is retained.
The agent writes structured memory after each email. Vendor patterns, deadlines, response habits. BM25 + time-decay retrieval without embeddings.
Most emails result in a quiet memory update. The agent fires tools — alerts, webhooks — only when its judgment says something actually requires attention.
Pipeline
A nano model pre-screens every email before full triage. This eliminates roughly 40% of LLM spend on clearly ignorable mail. The full triage model only runs when the pre-screen deems it necessary.
1. Pre-screen
gpt-4.1-nano classifies urgency. ~$0.0001/email.
2. Context load
Relevant memories retrieved via BM25 + time decay.
3. Full triage
gpt-4.1-mini analyzes, extracts entities, decides.
4. Tool execution
Alert, webhook, thread update — or nothing.
Privacy model
Vigil never connects to your inbox. No OAuth, no passwords, no API tokens to your email account. A standard forwarding rule sends a copy. The email body is processed in memory and discarded. Stop by deleting the forwarding rule.
No inbox access
Forwarding rules only
No stored bodies
SHA-256 hash proves receipt
No OAuth
No passwords or API tokens
You control it
Delete the rule to stop
Documentation
Agents with custom prompts and tools.
How it analyzes, remembers, and decides.
How context builds across all emails.
Forwarding rules and filter configuration.
Data flow, privacy model, what gets stored.
What is discarded. What is kept. Why.
REST API, webhooks, any framework.
Guided setup for Gmail and Outlook.