Novu Agent Inbox separates human replies from optional agent execution

A reply has a defined outcome

Novu’s November 2 announcement gives an existing agent its own email address, Telegram bot and Slack app through CLI or MCP. Agent Inbox can ask people for a decision and report approval, denial, waiting or expiry back to the calling workflow.

Execution needs a separate listener

Coding agents normally check messages only while running. Novu’s optional Claude Code listener can instead start work in a chosen project when the owner or a selected contact writes. Listening must be approved first; this is not automatic execution for every connected agent.

A narrower starting point

A communication address and an execution trigger are separate configuration choices. Novu describes initial email reception as a free demo until the inbox is claimed, which does not establish unlimited free service.

Engineers pair programming, December 2012; archival context, not Novu staff or the Agent Inbox interface. Photo: Vajrapani666 / Wikimedia Commons, CC BY‑SA 3.0. Display crops retain the same licence.

Share this article

Related News

NOAN provisions agents for new projects and separates free-plan keys

Hypertask adds agent ticket sharing with separate permission checks

Done adds project feedback and frozen receipts for agent work

Novu Agent Inbox separates human replies from optional agent execution

A reply has a defined outcome

Execution needs a separate listener

A narrower starting point

Sources

Tags

Novu Agent Inbox separates human replies from optional agent execution

A reply has a defined outcome

Execution needs a separate listener

A narrower starting point

Sources

Tags