Lux can check your inbox, list recent messages, and summarize threads. But she has one hard rule baked into her instructions: she never summarizes or infers what an email says until she has called inbox.detail and read the actual body. No fabrication. Ever.
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.
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.
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.
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.
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.
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.
We built this inbox integration from scratch. We can build the right version for your workflow.
Stark