Best Terminal Email Client (2026): aerc vs NeoMutt vs More

The short answer
The best terminal email client for most developers is aerc: a modern Go TUI with IMAP, notmuch and JMAP backends, plus OAUTHBEARER and XOAUTH2 login. Pick NeoMutt for maximum configurability and Himalaya for a scriptable CLI. All run on Linux, and none of them documents built-in AI triage or drafting.
aerc is the easiest terminal email client to start with: IMAP, notmuch, JMAP and native OAuth support. Compared with NeoMutt, Mutt, Himalaya and meli.
On this page
- 01The short answer: which terminal email client should you pick?
- 02What is aerc and how do I set it up with Gmail?
- 03aerc vs NeoMutt: which is better?
- 04How we compared these terminal clients
- 05Terminal email client comparison table
- 06aerc: the best terminal email client for most people
- 07NeoMutt: the power user's pick
- 08Mutt: the original, still stable
- 09Himalaya: a command line email client for scripts
- 10meli: the modern Rust TUI
- 11notmuch and alot: the tag-based mail workflow
- 12How to choose for your situation
- 13Where AI Emaily fits, and where it does not
The best terminal email client for most developers in 2026 is aerc, the mail TUI that needs the least setup while still handling threads, multiple accounts and scripting. NeoMutt and Mutt remain the power tools, while Himalaya and meli are the newer options. This guide covers what each costs to set up, how it shows HTML, how it signs in to Gmail, and where it still hurts.
A terminal mail client is a text-mode program you drive from the keyboard: no mouse, no web view, fast over SSH, and easy to script. The trade is work up front, usually config files, a Gmail sign-in step, and often a separate tool to fetch and index mail.
The short answer: which terminal email client should you pick?#
Start with aerc. Move to NeoMutt if you hit a customization wall, and to Himalaya if you want a CLI to script rather than an interface to live in. All of these are at home as a Linux terminal email client; if you would rather have a window, see our picks for graphical email clients for Linux and keyboard-driven email clients that are not terminal-only.
| Client | Pick it if | Setup cost |
|---|---|---|
| aerc | You want a modern TUI and the shortest route to reading mail | Low to medium |
| NeoMutt | You want to configure nearly everything | High |
| Mutt | You want the original, and to assemble the rest yourself | High |
| Himalaya | You want a CLI for scripts, not a TUI | Medium |
| meli | You want a newer TUI written in Rust | Medium |
| notmuch + alot | You think in tags and search, not folders | High |
Try aerc first, then reach for the others
What is aerc and how do I set it up with Gmail?#
aerc is a terminal email client written in Go, and the project calls itself "a pretty good email client" aimed at experienced users. The aerc mail TUI has vim-like keys, an ex-style command line, an embedded terminal for composing while you keep reading, built-in git-email workflows, and asynchronous IMAP and JMAP that keep the interface responsive on bad networks.
The route the aerc wiki documents for Gmail is an app password, which makes aerc a working terminal Gmail client with no OAuth setup. Your Google account needs 2-Step Verification turned on first.
- 1
Install aerc
Use your package manager. Arch, Debian and openSUSE all package it.
- 2
Create a Google app password
With 2-Step Verification on, create an app password for aerc in your Google Account. Google says you may not see this option on work or school accounts, or with Advanced Protection.
- 3
Run the new account wizard
In aerc, run the new-account command to start the wizard. Use imap.gmail.com for incoming mail and smtp.gmail.com for outgoing, as in the example below.
- 4
Add the Gmail settings
In accounts.conf set default to INBOX and postpone to the Gmail Drafts folder. Leave copy-to commented out, because Gmail's SMTP server files sent mail itself.
- 5
Turn on HTML mail
Install w3m, then uncomment the text/html filter in aerc.conf. It is off by default, so HTML-only mail won't display until you do this.
aerc vs NeoMutt: which is better?#
aerc is the better default and NeoMutt is the better endpoint. aerc gets you reading mail sooner; NeoMutt rewards the hours you put into it with more control over how everything works.
| aerc | NeoMutt | |
|---|---|---|
| Written in | Go, newer project | C, a mature fork of Mutt |
| Getting started | New account wizard | Hand-written config |
| HTML mail | text/html filter with w3m, shown inside aerc | auto_view plus a mailcap entry with copiousoutput |
| Gmail OAuth | OAUTHBEARER and XOAUTH2 in the source URL | External scripts |
| Extending it | Filters, templates, ex-style commands | Hooks, Lua, deep configuration |
| Also reads | Maildir, notmuch, mbox, JMAP | Maildir, mbox, notmuch, NNTP, POP |
How we compared these terminal clients#
We did not score these on a bench of installs and a stopwatch. We compared them on the capability dimensions that decide a terminal mail setup, each checked against the project's own documentation in November 2026.
- Setup cost: how much config, and how many helper tools, before you can read mail.
- Backends: IMAP, Maildir, notmuch, JMAP, mbox, and whether a separate sync tool is expected.
- HTML rendering: whether it can show HTML mail, and what it hands the job to.
- Gmail sign-in: whether it speaks OAUTHBEARER or XOAUTH2, and how you supply the token.
- Where it hurts: the honest rough edge each one carries.
Gmail sign-in is the sharp edge
Terminal email client comparison table#
Versions checked in November 2026: aerc 0.22.0 (Arch package), NeoMutt 2026-06-16, Mutt 2.4.3 (October 2026), Himalaya v2, meli 0.8.13 (January 2026). Open-source clients move quickly, so check each project before you commit.

| Client | Type | Backends | HTML mail | Gmail OAuth | Best for |
|---|---|---|---|---|---|
| aerc | Modern TUI (Go) | IMAP, Maildir, notmuch, mbox, JMAP | w3m through a filter, off by default | OAUTHBEARER/XOAUTH2 in the source URL; you supply a refresh token | Most developers |
| NeoMutt | TUI (C), Mutt fork | IMAP, POP, Maildir, mbox, notmuch, NNTP | External viewer via mailcap | External scripts | Power users who configure everything |
| Mutt | TUI (C) | IMAP, POP, Maildir, mbox | External viewer via mailcap | mutt_oauth2.py from its contrib folder | Purists and minimal setups |
| Himalaya | CLI, not a TUI (Rust) | IMAP, SMTP, JMAP, Gmail API, Microsoft Graph, Maildir, mbox | Limited: a CLI, not a viewer | A token broker; Himalaya reads the token from a command | Scripting and automation |
| meli | Modern TUI (Rust) | IMAP, Maildir, notmuch; mbox read-only; JMAP and NNTP functional | w3m by default, via a filter | use_oauth2 with a password command | A modern Rust client |
| notmuch + alot | Indexer + Python TUI | Local mail only (fetch with a separate tool) | External viewer | Handled by your sync tool | Tag- and search-first workflows |
aerc: the best terminal email client for most people#
aerc is the one to try first because it does the most without extra parts: IMAP, Maildir, notmuch, mbox and JMAP backends, threading with or without server support, PGP through GnuPG, and multiple accounts in one interface. For Gmail or Microsoft with OAuth, it speaks OAUTHBEARER and XOAUTH2 directly. Its manual says that with a token_endpoint set, the configured password is used as a refresh token, so you still have to obtain that token once.
Where it hurts: it is younger than Mutt, so a few deep customizations veterans expect are missing or done differently. Its notmuch support is also not as tag-native as a purpose-built notmuch frontend.
NeoMutt: the power user's pick#
NeoMutt is the choice when you want to configure everything. It is a maintained fork of Mutt, written in C, with the motto 'Teaching an Old Dog New Tricks'. You get a sidebar (that work was later adopted upstream into Mutt), notmuch integration, NNTP for newsgroups, and Lua, which its docs describe as limited for now to reading and setting config and running commands.
HTML needs a text/html entry in mailcap marked copiousoutput, typically a text browser like w3m, plus auto_view. Its guide describes OAuth as preliminary support through external scripts. Where it hurts: a working setup can mean hours in the manual and other people's dotfiles.
Mutt: the original, still stable#
Mutt is still maintained, with 2.4.3 tagged in October 2026. If you want a predictable base and are happy to add tools around it, it is a fine foundation. It supports IMAP, POP, Maildir and mbox, renders HTML through mailcap and an external viewer, and handles Gmail through mutt_oauth2.py, an example script in its contrib folder.
The classic pairing is Mutt with notmuch: notmuch indexes and tags, Mutt reads. Where it hurts: it is spartan out of the box, and you will assemble more of the workflow yourself than with aerc. Many people prefer to sync mail locally first with isync (mbsync).
Himalaya: a command line email client for scripts#
Himalaya is the odd one out on purpose: a CLI email client in Rust, not a TUI. You list and search your inbox from the command line with single commands, which makes it the natural fit for a cron job or a shell script that needs to check or send mail without a full client.
It supports IMAP, SMTP, JMAP, the Gmail REST API, Microsoft Graph, and local formats such as Maildir and mbox. Version 2 has no OAuth flow of its own: you use a token broker such as ortie and pass Himalaya a command that prints the token. A separate himalaya-tui is in active development. Where it hurts: reading threads all day in a CLI is awkward next to aerc or NeoMutt.
meli: the modern Rust TUI#
meli is a terminal client written in Rust. The latest tagged release we could confirm is v0.8.13, from January 2026, with development commits after it. Its project README rates IMAP, Maildir and notmuch as full support, mbox as read-only, and JMAP and NNTP as functional.
HTML uses w3m by default, and you can swap it with the pager's html_filter setting. For OAuth, meli.conf has a use_oauth2 option that works with server_password_command. Where it hurts: it has fewer worked examples and shared dotfiles than Mutt or NeoMutt, and its notmuch backend has no global search, so you search within a mailbox built from a query.
notmuch and alot: the tag-based mail workflow#
notmuch is not a mail client. It is a fast indexer built around search and tags rather than folders, and its site says plainly that it does no POP or IMAP. You point it at local mail, and a 'folder' becomes a saved search for a tag.
Frontends include alot (a Python TUI), Emacs, vim, and notmuch support inside aerc and NeoMutt, so you can adopt the model without abandoning your client. You fetch mail first with a sync tool such as isync (mbsync). Where it hurts: more moving parts than a single client, and a real mental switch if you think in folders. For heavy-search inboxes it is the most powerful approach here.
How to choose for your situation#
Match your main constraint to a tool and you will avoid the most common mistake in terminal email: reaching straight for the deepest client and giving up before mail arrives. Budget a couple of hours for the first setup, especially the Gmail step, and keep a working config to copy from.
| If you... | Pick | Because |
|---|---|---|
| want the least setup and a modern feel | aerc | A wizard, broad backends and native OAuth mechanisms |
| want to configure every keybinding and hook | NeoMutt | The deepest configuration surface here |
| want a minimal, stable base | Mutt (+ notmuch) | The original, small and predictable |
| want to script email, not live in a UI | Himalaya | Single commands you call from shell scripts |
| want a modern client written in Rust | meli | A TUI with modern backends |
| think in tags and search, not folders | notmuch (+ alot) | Fast indexed search and tagging as the core model |
Where AI Emaily fits, and where it does not#
We build AI Emaily, it is not a terminal client, and we kept it out of this ranking on purpose. There is no TUI and no Linux desktop build: it runs in a browser, as downloadable Mac and Windows apps, as an iPhone app, and as an installable web app on Android. If you want a text-mode mail reader, pick aerc or NeoMutt, because on that job they beat us.
The adjacent thing we do is for readers whose real goal is scripting, not the text UI. AI Emaily has a REST API and an MCP server, so a script on your Linux box or an AI agent you run can search, triage and draft. Sending is a separate, explicit confirm step with an undo window, and actions are audited. Drafts draw on the Personal Context you set plus per-client profiles.
This is programmatic access, not a terminal interface. API core scopes come with Pro; all scopes and MCP need Autopilot or Team. It is a paid product with a 7-day free trial on Pro or Autopilot and no free plan; see current plans.
Frequently asked
See it in AI Emaily
Keep reading
Sources

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.