Appearance
Himalaya
Himalaya CLI: IMAP/SMTP email from terminal.
Skill metadata
| Source | Bundled (installed by default) |
| Path | skills/email\himalaya |
| Version | 1.1.0 |
| Author | community |
| License | MIT |
| Platforms | linux, macos, windows |
| Tags | Email, IMAP, SMTP, CLI, Communication |
Reference: full SKILL.md
INFO
The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
Himalaya Email CLI
Himalaya is a CLI email client that lets you manage emails from the terminal using IMAP, SMTP, Notmuch, or Sendmail backends.
This skill is separate from the Hermes Email gateway adapter. The gateway adapter lets people email the agent and uses Hermes' built-in IMAP/SMTP adapter; this skill lets the agent operate a mailbox from terminal tools and requires the external himalaya CLI.
References
references/configuration.md(config file setup + IMAP/SMTP authentication)references/message-composition.md(MML syntax for composing emails)
Prerequisites
- Himalaya CLI installed (
himalaya --versionto verify) - A configuration file at
~/.config/himalaya/config.toml - IMAP/SMTP credentials configured (password stored securely)
Installation
bash
# Pre-built binary (Linux/macOS — recommended)
curl -sSL | PREFIX=~/.local sh
# macOS via Homebrew
brew install himalaya
# Or via cargo (any platform with Rust)
cargo install himalaya --lockedConfiguration Setup
Run the interactive wizard to set up an account:
bash
himalaya account configureOr create ~/.config/himalaya/config.toml manually:
toml
[accounts.personal]
email = "you@example.com"
display-name = "Your Name"
default = true
backend.type = "imap"
backend.host = "imap.example.com"
backend.port = 993
backend.encryption.type = "tls"
backend.login = "you@example.com"
backend.auth.type = "password"
backend.auth.cmd = "pass show email/imap" # or use keyring
message.send.backend.type = "smtp"
message.send.backend.host = "smtp.example.com"
message.send.backend.port = 587
message.send.backend.encryption.type = "start-tls"
message.send.backend.login = "you@example.com"
message.send.backend.auth.type = "password"
message.send.backend.auth.cmd = "pass show email/smtp"
# Folder aliases (himalaya v1.2.0+ syntax). Required whenever the
# server's folder names don't match himalaya's canonical names
# (inbox/sent/drafts/trash). Gmail is the common case — see
# `references/configuration.md` for the `[Gmail]/Sent Mail` mapping.
folder.aliases.inbox = "INBOX"
folder.aliases.sent = "Sent"
folder.aliases.drafts = "Drafts"
folder.aliases.trash = "Trash"Heads up on the alias syntax. Pre-v1.2.0 docs used a
[accounts.NAME.folder.alias]sub-section (singularalias). v1.2.0 silently ignores that form — TOML parses fine, but the alias resolver never reads it, so every lookup falls through to the canonical name. On Gmail this means save-to-Sent fails after SMTP delivery succeeds, andhimalaya message sendexits non-zero. Any caller (agent, script, user) that retries on that exit code will re-run the entire send — including SMTP — producing duplicate emails to recipients. Always usefolder.aliases.X(plural, dotted keys, directly under[accounts.NAME]).
Hermes Integration Notes
- Reading, listing, searching, moving, deleting all work directly through the terminal tool
- Composing/replying/forwarding — piped input (
cat << EOF | himalaya template send) is recommended for reliability. Interactive$EDITORmode works withpty=true+ background + process tool, but requires knowing the editor and its commands - Use
--output jsonfor structured output that's easier to parse programmatically - The
himalaya account configurewizard requires interactive input — use PTY mode:terminal(command="himalaya account configure", pty=true)
Common Operations
List Folders
bash
himalaya folder listList Emails
List emails in INBOX (default):
bash
himalaya envelope listList emails in a specific folder:
bash
himalaya envelope list --folder "Sent"List with pagination:
bash
himalaya envelope list --page 1 --page-size 20Search Emails
bash
himalaya envelope list from john@example.com subject meetingRead an Email
Read email by ID (shows plain text):
bash
himalaya message read 42Export raw MIME:
bash
himalaya message export 42 --fullReply to an Email
To reply non-interactively from Hermes, read the original message, compose a reply, and pipe it:
bash
# Get the reply template, edit it, and send
himalaya template reply 42 | sed 's/^$/\nYour reply text here\n/' | himalaya template sendOr build the reply manually:
bash
cat << 'EOF' | himalaya template send
From: you@example.com
To: sender@example.com
Subject: Re: Original Subject
In-Reply-To: <original-message-id>
Your reply here.
EOFReply-all (interactive — needs $EDITOR, use template approach above instead):
bash
himalaya message reply 42 --allForward an Email
bash
# Get forward template and pipe with modifications
himalaya template forward 42 | sed 's/^To:.*/To: newrecipient@example.com/' | himalaya template sendWrite a New Email
Non-interactive (use this from Hermes) — pipe the message via stdin:
bash
cat << 'EOF' | himalaya template send
From: you@example.com
To: recipient@example.com
Subject: Test Message
Hello from Himalaya!
EOFOr with headers flag:
bash
himalaya message write -H "To:recipient@example.com" -H "Subject:Test" "Message body here"Note: himalaya message write without piped input opens $EDITOR. This works with pty=true + background mode, but piping is simpler and more reliable.
Move/Copy Emails
Move to folder (target folder comes first, then the message ID):
bash
himalaya message move "Archive" 42Copy to folder (target folder comes first, then the message ID):
bash
himalaya message copy "Important" 42Delete an Email
bash
himalaya message delete 42Manage Flags
Add flag:
bash
himalaya flag add 42 --flag seenRemove flag:
bash
himalaya flag remove 42 --flag seenMultiple Accounts
List accounts:
bash
himalaya account listUse a specific account:
bash
himalaya --account work envelope listAttachments
Save attachments from a message:
bash
himalaya attachment download 42Save to specific directory:
bash
himalaya attachment download 42 --downloads-dir ~/DownloadsOutput Formats
Most commands support --output for structured output:
bash
himalaya envelope list --output json
himalaya envelope list --output plainDebugging
Enable debug logging:
bash
RUST_LOG=debug himalaya envelope listFull trace with backtrace:
bash
RUST_LOG=trace RUST_BACKTRACE=1 himalaya envelope listTips
- Use
himalaya --helporhimalaya <command> --helpfor detailed usage. - Message IDs are relative to the current folder; re-list after folder changes.
- For composing rich emails with attachments, use MML syntax (see
references/message-composition.md). - Store passwords securely using
pass, system keyring, or a command that outputs the password.