Skip to main content

​
Email

Pawz can read and send email through your existing accounts using Himalaya, an IMAP/SMTP CLI client.

​
Prerequisites

Install Himalaya:

​
Configuration

Himalaya uses a TOML config file at ~/.config/himalaya/config.toml:

​
Skills setup

Enable the Email skill in the Skills tab and provide: :::tip For Gmail, use an App Password — not your regular password. :::

​
Agent tools

With the Email skill enabled, agents get:

​
Mail permissions

Each account can have granular permissions:

​
Provider icons

The mail view auto-detects your provider and shows the appropriate icon:

​
Provider presets

The account setup wizard auto-fills IMAP/SMTP settings for popular providers: :::info All connections use TLS encryption. Passwords are stored in the OS keychain (macOS Keychain / libsecret on Linux), never in plain text files. :::

​
Email filtering and folders

Agents can work with email folders to organize messages:

​
Folder support

Himalaya supports standard IMAP folders:
  • INBOX — default inbox
  • [Gmail]/All Mail — Gmail archive
  • [Gmail]/Drafts — drafts folder
  • Sent / [Gmail]/Sent Mail — sent items
  • Custom folders created by the user

​
Attachment handling

Email attachments are managed through the Himalaya CLI:
  • Reading — email_read retrieves the full message body including inline content
  • Downloading — the agent can save attachments to the local filesystem via Himalaya commands
  • Sending — attachments can be included when composing messages through the Himalaya skill

​
AI email actions

The mail view includes built-in AI actions for each email. These send a pre-composed prompt to your agent:

​
Compose and reply

The built-in compose modal supports:
  • Reply — pre-fills the recipient and subject with Re: prefix
  • Forward — pre-fills the subject with Fwd: prefix and includes the original message
  • New email — opens the chat with a compose prompt for the agent to draft and send
:::tip For AI-composed messages, the agent drafts the email and uses Himalaya to send it. All outgoing email through the email_send tool requires human-in-the-loop (HIL) approval — you must confirm before any email is actually sent. :::

​
Credential Vault

Email accounts are protected by the Credential Vault with a full audit trail:
  • Permission toggles — enable/disable read, send, delete, and manage permissions per account
  • Activity log — every agent email action is logged with timestamps
  • Blocked actions — attempts to use a disabled permission are logged and denied
  • Revoke access — instantly remove an account and delete credentials from the device

​
Channel integration

Email can also be set up as a channel — see Channel Routing for details.