Emailclaw

Why it's ranked here

The idea is specific and well carried through. Mail threads map one to one onto tasks, risky tool calls pause for a four-digit code you reply with, and silence, a wrong code or a reply from another thread all count as refusal. It ships as installers for Windows, macOS and two Linux formats from a tagged release pipeline, under MIT. Against that, the release build skips tests, the hosted relay carries no service guarantee, and the loosest permission mode is one setting away. A thoughtful design worth trying on a spare mailbox, not yet something to trust with a primary account.

What's good

The approval flow is the strongest part. A pending approval shows the tool, a parameter summary, the risk level and a countdown, and the reply code is intercepted before it reaches the model, so it never pollutes the task context. A failed delivery of the approval message rejects the call rather than letting it through. Sender allowlisting limits who can start work. The same startup code powers the desktop app and a systemd background service, and both share one data folder, so moving to a server needs no config migration. Plugins dropped into a folder are picked up within about five seconds without a restart.

Tradeoffs

Building from source needs JDK 25, and the tagged release job packages with tests skipped even though test libraries are declared. The optional hosted mail relay is offered with no quality guarantee, can change terms without notice, deletes messages after 15 minutes and drops accounts idle for 100 days. Attachments are capped at a single 10 MB file per message. Permission modes run up to a full bypass, and the sample coding plugin accepts arbitrary extra flags, including one that disables its own sandbox. The local API admits unauthenticated calls from the loopback addresses by default.

How to use it well

Give it a dedicated mailbox with an app password, never your main account, and keep the allowed senders list to addresses you control. Start agents in the read-only or routine-confirmation mode, as the manual advises, and test the model connection in the desktop chat before wiring up mail. It suits people who already live in their inbox and want recurring research digests or document tasks kept apart by thread. It is not a team inbox tool, and it does not replace a coding agent: the coding plugins only shell out to external command-line tools.

Observed

License

MIT (LICENSE)

Language

Java, built with Maven, compiler release 25 (emailclaw/pom.xml)

Agent framework

AgentScope Java with its harness module (emailclaw/pom.xml)

Packaging

Windows .exe, macOS .dmg, Linux .deb and .tar.gz built by jpackage (.github/workflows/release.yml)

Interfaces

JavaFX desktop app plus headless service mode via --service flag (emailclaw/src/main/java/ai/emailclaw/emailclaw/Launcher.java)

Mail transport

IMAP polling, minimum 5 second interval, SMTP replies (docs/Emailclaw-User-Manual.md)

Extension surface

Java SPI and external JAR plugins for tools, providers, hooks, channels and UI (plugin-samples/PLUGIN-DEVELOPER-GUIDE.md)

Release build

Packages with -DskipTests (.github/workflows/release.yml)

Unauthenticated API hosts

Loopback addresses 127.0.0.1 and ::1 by default (emailclaw/src/main/java/ai/emailclaw/emailclaw/model/SecuritySettings.java)