Email triage in conversation —
with one unbreakable rule.
Lux checks your inbox, lists messages, and summarizes threads, but never infers an email until she has read the actual body via inbox.detail. No fabrication, ever.
What Lux can do with Inbox.
Data before summary
Lux's inbox instructions include an explicit hard rule: NEVER summarize, paraphrase, guess, or infer email content from the subject line alone. inbox.detail must be called first. Violating this rule is labeled as giving the user false information.
Check, list, detail
inbox.check gives a quick count overview and the 5 most recent unhandled messages. inbox.recent lists up to 25 with status filters. inbox.detail returns the full body, sender, AI analysis, and linked task for a single message.
Pre-computed intelligence
inbox.detail returns a pre-computed AI analysis field alongside the raw body — category, sentiment, required action. Lux reports on it without re-analyzing on the fly, keeping responses fast and consistent.
No ID required
inbox.detail locates a message by request_id, sender name, or subject. Lux doesn't need the exact database ID. "What did David want?" routes to the right message automatically via name lookup.
Five-stage triage flow
Messages flow through triage → new → claimed → in_progress → dismissed. Lux can filter by any status — useful for reviewing only unhandled messages or everything currently being worked on.
Email + board in one view
inbox.detail returns the linked task ID if one exists — Lux can show the associated board task alongside the email summary, keeping the full work context in a single response.
Want email triage wired into your AI interface — with data integrity built in?
We built this inbox integration from scratch. We can build the right version for your workflow.
// more from the engine room
Other builds from Stark Dev
StarkX is one of several products we've built in-house. Same engine room, different problem.