Triage Queue

Live view of incoming emails and how they were routed.
LLM: stub local_files Dry-run

Inbox

0
Loading…

Detail

Select an email to see its triage detail and any drafted reply.
Model Providers Actions Triage Rules Examples Environment

Backend

stub

Configure

Select a provider on the left.

Token usage

Tokens pushed through each backend this session (resets on restart). est. means counted locally where the model didn't report usage.

No model calls yet.

Actions per intent

For each intent the model can assign, decide what happens and where it goes. {fields} in folders/notes are filled from the email's extracted data. Drafts are never auto-sent unless you tick send. Saved changes are validated and hot-reloaded — no restart.

Loading…

Triage rules

Edit the intents and routing below. Changes are validated, saved to disk, and hot-reloaded — no restart.

Current setup

Use case
—
Intents
—
Routing
—

Example library

0

Labelled past emails the model references during triage. The 6 most relevant are injected per email. Add up to ~100 as .yaml/.json/.jsonl in .

Runtime environment

Read-only infrastructure wiring (set via environment / .env). Ingestion sources, send mode, and connector credentials live here.