slm_email · Productivity · 10-Plane Pure-CPU Agent

SLM Email Assistant

Securely processes your incoming inbox streams. Auto-drafts contexts, filters spam, and extracts urgent action items on standard CPUs.

01 / Overview & Capabilities

Securely processes your incoming inbox streams. Auto-drafts contexts, filters spam, and extracts urgent action items on standard CPUs.

Key Features

  • Offline spam classifier and classification tagging
  • Action item extraction and scheduled task planning
  • Generates contextual email replies matching your custom tone profile
  • PII protection — zero emails ever leave your machine

02 / Standalone OS Harness Installers, CLI & Python SDK

In SLMAgents 2.0, SLM Email Assistant executes inside the 10-Plane Pure-CPU Agent Harness (slm_harness). Download a self-extracting Individual Agent + Harness OS Installer for macOS, Windows, or Linux (bundling slm_email + slm_harness + the ./slm CLI), install the full 26-agent desktop suite, or install via Python pip:

1. Individual SLM Email Assistant + 10-Plane Harness Installers (All OSes)

2. Full 26-Agent Studio & Desktop OS Installers

3. 10-Plane Harness CLI (./slm) & Python pip Installation

Terminal — 10-Plane Harness CLI & Pip
# Option A: Install via PyPI or editable source with the 10-Plane Harness
$ pip install slm-email
$ pip install -e ./slm_harness -e ./slm_email

# Option B: Run directly through the Unified 10-Plane Pure-CPU Harness CLI (./slm)
$ ./slm ask "Triage this email thread, extract action items, and draft a concise executive reply"
$ ./slm chat   # Interactive Rich TUI with 18 slash commands (/trace, /models, /arena, /undo)
$ ./slm serve  # 100% Offline Web AI Studio + OpenAI /v1 API at http://127.0.0.1:7860

03 / 10-Plane Pure-CPU Harness Integration (slm_harness)

Rather than executing as an isolated prompt wrapper, SLM Email Assistant is natively orchestrated by the SLMAgents 2.0 10-Plane Pure-CPU Harness (via slm_harness.runtime.legacy_bridge and CascadeRouter). Every call benefits from hybrid llama.cpp GGUF (Q4_K_M) + Quantized INT4/INT8 CPU execution, watermarked LRU memory governance, grammar-constrained decoding, and deterministic verification at $0 API cost:

Harness PlaneSubsystemHow It Powers SLM Email Assistant on Pure CPU
Plane 6 CascadeRouter (<35ms) Stage 1 (.eml / .mbox MIME Inspection) & Stage 3 (1024-d Embedding Margin)
Plane 2 & 5 MemoryArena & Hybrid CPU Runtime Specialist Role: primary (Qwen3-4B GGUF Q4_K_M / Llama-3.2-3B INT4). Managed inside Watermark LRU MemoryArena (lite 2.6 GB / balanced 4.7 GB / power 8.2 GB) with zero-copy session sharing and automatic OOM tier step-down (8B -> 4B -> 3B -> 0.8B).
Plane 7 & 8 Deterministic Verifier & Governance Plane 2 GBNF Triage & Action-Item Schema + Plane 8 Outbound PII/Secret Redaction Scrubber
Plane 1, 3 & 4 Kernel, Artifact Scratchpad & 4-Tier Memory SQLite WAL CheckpointStore (/fork, /rewind, /undo), content-addressed artifact://<sha12> handles to prevent prompt bloat, and hybrid SQLite FTS5 BM25 + HNSW vector memory.

04 / Source Checkout (Git Sparse-Checkout)

Clone this agent alongside the 10-Plane Pure-CPU Harness (slm_harness) from the monorepo using Git sparse-checkout — no need to download all 26 agents:

Option 1 — Sparse Checkout with 10-Plane Harness (Recommended)

Terminal — Git Sparse Checkout
# 1. Create and enter a new directory
$ mkdir slm_email_workspace && cd slm_email_workspace

# 2. Initialise empty git repo and add remote
$ git init
$ git remote add origin https://github.com/t00114218-stack/SLMAgents.git

# 3. Enable sparse-checkout for both slm_harness and slm_email
$ git sparse-checkout init --cone
$ git sparse-checkout set slm_harness slm_email

# 4. Pull the 10-Plane Harness and agent source
$ git pull origin main

Option 2 — Full Repository Clone

Terminal — Full Clone
$ git clone https://github.com/t00114218-stack/SLMAgents.git
$ cd SLMAgents
$ ./slm doctor

Note: After checkout, install the harness and agent in editable mode with pip install -e ./slm_harness -e ./slm_email or download the pre-packaged OS Harness Installer above.

05 / Configuration & API Reference

Constructor Parameters

Instantiate SLMEmailAssistant with performance options:

ParameterType / DefaultDescription
model_pathstr | NoneExplicit path to GGUF (Q4_K_M) or quantized ONNX model weights. If omitted, managed automatically by the 10-Plane Harness MemoryArena.
cache_dirstr | NoneDirectory to store model weights offline. Defaults to ~/.cache/slm-email/. Also settable via SLM_EMAIL_ASSISTANT_CACHE_DIR.
n_threadsint | 4CPU thread count for 10-Plane Harness inference (auto-tuned to physical P-cores). Optimize for CPU core count. Also settable via SLM_EMAIL_ASSISTANT_N_THREADS.

Methods

Method SignatureReturn TypeDescription
process_email(email_text, system_prompt=None, user_input=None)dictProcesses incoming mail to filter spam, extract action deadlines, and formulate contextual replies.

Method Parameters (Execution Customization)

All main execution methods accept optional system routing parameters:

ParameterType / DefaultDescription
system_promptstr | NoneOptional custom system prompt instruction to override the default system template response parameters.
user_inputstr | NoneOptional additional user-supplied target text variables or contextual keys.

Quick Start

from slm_email import SLMEmailAssistant

assistant = SLMEmailAssistant()
reply = assistant.process_email(
    email_text,
    system_prompt="Draft response in a formal corporate tone",
    user_input="Include attachment reminder"
)
print(reply)

Environment Variables

Configure agent parameters globally using environment values:

Environment VariableDefaultPurpose
SLM_EMAIL_ASSISTANT_N_THREADS4Sets CPU inference execution threads.
SLM_EMAIL_ASSISTANT_CACHE_DIR~/.cache/slm-email/Default directory to store local GGUF (Q4_K_M) and quantized INT4/INT8 model weights (shared with ~/.slm_harness/models).

CPU Performance Tuning

To run the SLMEmailAssistant engine efficiently on CPU under 1.5 GB memory footprint:

  • Match Threads to Core Count: Set n_threads or SLM_EMAIL_ASSISTANT_N_THREADS to match the physical CPU core count.
  • Sequential Processing: Avoid concurrent processing when batch files are large.
  • Garbage Collection: Clear variables and run gc.collect() to release model RAM blocks after execution.

Verified Input & Output Logs

Diagnostic execution console response running locally on CPU:

→ INPUT:
"Please submit the report by Friday."

← OUTPUT:
{
  'is_spam': False,
  'action_items': ['Please submit the report by Friday.']
}