AI Email Client
IMAP/SMTP for mail, an LLM (DeepSeek by default) for the intelligence. One API route (POST /api/v1/mail) dispatches on an action field; the browser UI is served on the same port. Actions actionwhat it doesinboxFetch the inbox over IMAP and triage each email (category, priority, summary, folder).
- ▪IMAP/SMTP for mail, an LLM (DeepSeek by default) for the intelligence.
- ▪One API route (POST /api/v1/mail) dispatches on an action field; the browser UI is served on the same port.
- ▪Actions actionwhat it doesinboxFetch the inbox over IMAP and triage each email (category, priority, summary, folder).
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,992 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Kdeps |
| Canonical URL | https://kdeps.io/packages/kdeps-ai-email-client |
| Publication time | Thu, 06 Aug 2026 15:41:42 +0000 |
| Retrieval time | 2026-08-06T15:50:43.013Z |
| Last seen | 2026-08-06T15:50:43.013Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
kdeps-ai-email-clientworkflowv1.0.0AI email client — triage, summarize, draft, reorganize labels, and unsubscribe, with a web UIInstallkdeps registry install kdeps-ai-email-clientThen run locally:kdeps exec kdeps-ai-email-clientConfigure LLM provider in ~/.kdeps/config.yaml (created automatically on first run).READMEai-email-client An AI email client as a kdeps workflow: triage, summarize, draft, reorganize labels, and unsubscribe — with a single-page web UI. IMAP/SMTP for mail, an LLM (DeepSeek by default) for the intelligence. One API route (POST /api/v1/mail) dispatches on an action field; the browser UI is served on the same port. Actions actionwhat it doesinboxFetch the inbox over IMAP and triage each email (category, priority, summary, folder).
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Kdeps.
Discussion
0 commentsMore from Kdeps
