The angel command
angel is Angel Mail from a shell, for agents that work better with commands than with MCP (Grok Bot, Hermes, scripts, cron). It calls the same /mcp endpoint with the same tokens, so everything it writes lands in Agent drafts and every permission check applies. Node 22, no packages.
Install and sign in #
git clone https://github.com/PirateKing44/Angel-Mail
ln -sf "$PWD/Angel-Mail/cli/sterling.mjs" ~/.local/bin/angel
angel login # asks for your server's address once, then a token (not echoed)
Make the token in Angel Mail → Settings → AI connections, one per agent, named after it: the queue shows that name. angel login checks it, then keeps it in the macOS Keychain (service angel-mail) or in ~/.config/angel-mail/token (mode 600). Or set ANGEL_MAIL_TOKEN and ANGEL_MAIL_URL (for the hosted service, https://app.angelmail.io).
Commands #
angel accounts # linked inboxes
angel search "from:jordan newer_than:7d" # [--account a@b] [--folder inbox] [--limit 20]
angel thread <thread-id>
angel draft --to "Jordan <jordan@example.com>" --subject "Pilot" --body-file note.md [--attach deck.pdf]
angel draft --reply-to <thread-id> [--reply-all] --body "Thursday works."
angel request-send …same flags… # ready to go: "Wants to send"
angel request-send --draft-id <draft-id> # ask for an existing draft
angel drafts [--status returned] # your items and what the owner did
angel review <review-id> # their edits, or their note
angel wait <review-id…> [--timeout 50] # returns as soon as they act on one
angel revise <review-id> --body-file v2.md # same item, next version
angel feedback [--account a@b] # how the owner edits drafts
angel propose --file proposal.json # inbox actions for their approval
angel reminders · angel remind <thread-id> "tomorrow 9am"
angel workflows # the named workflows
angel workflow <name> [--account a@b] [--arg key=value …] # print a workflow's steps
angel tools · angel call <tool> '<json>' # any tool directly
--json prints the server's answer as JSON; the default is readable text. --body-file - reads standard input. Local files are sent as base64 (over about 3 MB it warns: put big files at a public https URL and attach that).
Exit codes: 0 ok, 2 bad input, 3 auth (no token, refused token, inbox not linked), 4 not found, 5 server or network. Errors are one line on stderr.
Workflows from a shell #
angel workflows
angel workflow write_email --arg to=jordan@example.com --arg about="move Thursday's call to Friday"
prints the steps for an agent to follow, the same text MCP clients get from prompts/get. The steps name MCP tools; from a shell each one is angel call <tool> '<json arguments>' (or the matching command above). Hand it to any agent that can run angel:
claude -p "$(angel workflow sort_inbox)" --allowedTools "Bash(angel *)"
Draft, wait, revise #
id=$(angel draft --to marcus@example.com --subject "Kickoff" --body-file note.md --json | node -pe 'JSON.parse(require("fs").readFileSync(0)).review_id')
angel wait "$id" # the owner sends it back with a note…
angel review "$id" # …read it
angel revise "$id" --body-file note-v2.md
A worker #
angel worker makes an always-on computer do Angel Mail's AI jobs with Claude Code or Codex on the owner's own plan. It uses its own worker token (smw_, Settings → AI connections → Add a worker), never an agent token:
angel worker login
angel worker --once # take one job, to try it
angel worker [--engine codex]