Files

T

AIPassand@devpulse e42f4ddeaf feat(system): feat(system): S82: all branch audit fixes + prax 100% + drone backup removed + seedgo --help + ai_mail cascade fix + memory rollover + spawn template_owners + flow fixes + Medic investigation (#210 )

* feat(system): feat(system): S82: core 10 cleanup — AGENTS/GEMINI prompts, STATUS.local, sandbox + vision docs, branch fixes

Co-Authored-By: @devpulse <devpulse@aipass>

* feat(system): feat(system): S82: all branch audit fixes + prax 100% + drone backup removed + seedgo --help + ai_mail cascade fix + memory rollover + spawn template_owners + flow fixes + Medic investigation

Co-Authored-By: @devpulse <devpulse@aipass>

---------

Co-authored-by: @devpulse <devpulse@aipass>

2026-04-09 21:57:57 -07:00

3.3 KiB

Raw Blame History

← Back to AIPass

AI_MAIL

Purpose: Inter-agent messaging for AIPass. File-based email system that lets agents send, receive, and process messages using @branch addresses. No SMTP, no external services — just JSON files and symbolic routing. Module: aipass.ai_mail Created: 2025-11-08 Last Updated: 2026-04-07

Status: Operational. Core email workflow (send/inbox/reply/close), dispatch system (with startup timeout + auto-retry), daemon, desktop notifications all working. Seedgo 99%.

Commands / Usage

drone @ai_mail dispatch @target "Subject" "Body"          # Send dispatch email + wake
drone @ai_mail dispatch @target "Subject" "Body" --fresh  # Send + fresh wake
drone @ai_mail email @target "Subject" "Body"             # Send email (no wake)
drone @ai_mail dispatch wake @target                      # Wake only (no email)
drone @ai_mail inbox                                      # Check inbox
drone @ai_mail --help                                     # Full help

Email Lifecycle

Messages follow a 3-state model:

new → opened → closed

new — Delivered to inbox, never viewed
opened — Viewed by recipient, awaiting action
closed — Replied or dismissed, archived automatically

Dispatch System

The dispatch command sends an email and wakes the target branch in one step. A polling daemon can also watch inboxes and spawn agents for auto_execute dispatch emails automatically.

Agents are ephemeral (wake, do work, exit)
Safety limits: max turns per wake, max dispatches per branch per day
PID-based locking prevents concurrent agents per branch
Startup health check: monitors JSONL session files for 90s, kills if no activity
Auto-retry: 3 strikes (resume, resume, fresh) before bounce
Failed agents trigger bounce emails back to sender

Architecture

Follows the standard AIPass 3-layer pattern:

ai_mail/
├── apps/
│   ├── ai_mail.py          # Entry point (auto-discovers modules)
│   ├── modules/
│   │   ├── email.py        # Send, inbox, view, reply, close, contacts
│   │   ├── dispatch.py     # Dispatch status, daemon, wake
│   └── handlers/
│       ├── email/           # Delivery, formatting, inbox ops, purge, reply
│       ├── dispatch/        # Daemon, wake, dispatch_monitor, status
│       ├── registry/        # Branch registry read
│       ├── users/           # Branch detection, user lookup
│       ├── json_utils/      # JSON I/O helpers (load_json, save_json)
│       ├── paths.py         # Shared find_repo_root() utility
│       ├── notify.py        # Desktop notifications (dbus)
│       └── central_writer.py # Central inbox stats aggregation

Integration Points

Depends On

aipass.prax — Logging via system_logger
aipass.cli — Console output and display formatting
aipass.drone — Command routing and @branch resolution
Python stdlib (pathlib, json, argparse, importlib)

Provides To

All modules — inter-branch messaging (send/receive/reply/close)
Dispatch system — autonomous task execution via --dispatch flag
Branch contacts — address book for @branch routing

Last Updated: 2026-04-07