What's New

New features, improvements, and fixes — shipped continuously.

For longer reads, tutorials, and research, visit the blog. For the full technical changelog, see the docs.

v0.3.1
v0.3.1
✦ Latest

Organization and mailbox webhooks

Paid plans can now receive signed HTTP callbacks for email, mailbox, and recipient-consent events, scoped to an organization or a single mailbox.

What’s New

Webhooks

Broodnet can now send signed HTTP POST requests when activity occurs in your organization. Use them to start an autonomous triage run when mail arrives, update an internal system after a consent decision, or route agent activity into your own monitoring.

Choose the scope that matches the workflow:

  • Organization: receive selected events from every mailbox in the organization, including mailbox creation and deletion
  • Mailbox: receive email events and consent requests from one mailbox only

Available events cover email received, sent, and blocked; mailboxes created and deleted; and recipient consent requested, approved, and denied. Consent decisions are organization-scoped because approval applies across the organization.

Signed delivery and retries

Every request uses the Standard Webhooks 1.0 HMAC-SHA256 format, including a signed delivery ID and attempt timestamp. The whsec_ signing secret is shown once when the webhook is created and can be rotated from the dashboard.

The Broodnet webhook reference documents the delivery headers, signed content, verification example, payload envelope, retries, and event catalog.

Endpoints that require their own credentials can receive one custom authentication header with every delivery. This works with bearer tokens, API keys, and agent runtimes such as OpenClaw without putting credentials in the webhook URL. Header values are stored encrypted.

Failed deliveries are retried automatically. The delivery history records response codes, errors, attempt counts, and payloads so you can inspect each callback without leaving Broodnet. Endpoints can also be paused when a consumer is offline.

Get started

Open Webhooks in the dashboard, choose an organization or mailbox scope, select the events you need, and add your HTTPS endpoint. If the receiver requires a token or API key, add its authentication header before creating the webhook.

v0.3.0
v0.3.0

Outbound policy and recipient consent

Agents can now email external recipients through explicit recipient consent or a recent reply window. A new outbound policy page puts mute, recipient consent, and reply window controls in your dashboard.

What’s New

Organizations can now send email to external addresses through explicit recipient approval. Here’s how it works:

  1. Request consent for an external email address from the new Outbound Policy page (/app/policy)
  2. Broodnet sends the recipient a private review link — no account required on their end
  3. The recipient approves or denies
  4. Once approved, mailboxes in your organization can send to that address

Consent links are bearer tokens delivered only by Broodnet email. They never appear in API responses, audit logs, webhook payloads, or the dashboard.

Admins can revoke a previously approved recipient at any time.

Reply window

A mailbox can now reply to an external sender that recently emailed that same mailbox. Scoped tightly — only the specific mailbox that received the inbound message, within a configurable time window (default 72 hours). No consent request needed for transient interactions like OTP replies or support ticket responses.

Mute mode

A new policy overlay that restricts mailboxes to organization members only. Sibling mailbox email and external rules are disabled while mute is on. Stored consent and reply window settings are preserved and restored when mute is turned off.

Blocked attempts

When a mailbox tries to send to an external address that isn’t covered by any policy rule, the attempt is rejected and recorded as an email_blocked audit event. Operators can search those events by recipient address in the audit log.

Dashboard integration

The new Outbound Policy page (/app/policy) is in your dashboard sidebar under “Outbound policy”. It shows mute, consent records, and reply window controls in a single view.

Admins and owners can toggle all settings and revoke approved recipients. Members can request consent and dismiss pending requests but cannot change policy settings.

CLI support for agents

Agents using mailbox tokens can inspect consent availability and request approval without an organization API key:

broodnet mail consent --json
broodnet mail consent request [email protected] --note="Need approval for support replies" --json
broodnet mail consent list --status=pending --json

mail consent --json returns the live policy state for the mailbox, including canRequest, reason, stored settings, effective settings, and plan gates. If consent requests are unavailable, agents should report reason instead of guessing whether the account needs an upgrade, an operator setting change, or postmaster configuration.

mail consent request sends one consent email when policy allows it. Existing approvals, active pending requests, and internal organization recipients are returned as structured results instead of sending duplicate email. Policy failures return code: "POLICY" in JSON mode.

mail consent list shows consent lifecycle rows for the organization: pending, approved, denied, and revoked. It is not a full address book and does not include sibling mailboxes or organization members.

Pricing

Recipient consent and reply window appear in the feature list for all paid plans (Founder, Pro, Team, Unlimited). Free plans keep the current internal-only behavior — mailboxes can email organization members and sibling mailboxes, nothing else.

Learn more

v0.2.3
v0.2.3

CLI: watch, mark, inbox filters

The CLI gets a batch of agent-quality-of-life upgrades: wait for the next email to arrive, filter and paginate your inbox, and flip message flags without touching the TUI.

What’s New

mail watch — wait for the next email

Designed for OTP and verification flows. Run it after triggering a sign-up or password reset and it will open the arriving message automatically — no polling loop needed in your agent script.

broodnet mail watch --json

Opens immediately if a message arrived in the last 60 seconds. Otherwise polls every 3s for up to 60s and opens the first arrival. Returns the same shape as mail open.

mail inbox — filters, pagination, sort

The inbox command now filters server-side so it stays fast on large mailboxes.

  • Flag filters: --unread, --read, --important, --answered, --unanswered — combinable
  • Pagination: --limit and --offset for walking through large inboxes page by page
  • Sort order: --sort=oldest to flip the default newest-first ordering
  • Response metadata: the JSON response now includes total and the active filter set
broodnet mail inbox --unread --important --limit=20 --offset=20 --json

mail mark — set and clear flags

Mark messages as read, unread, flagged, or unflagged by UID without opening or deleting them. Accepts multiple UIDs in one call.

broodnet mail mark 1042 --seen
broodnet mail mark 10 11 12 --flagged

mail open — leaner JSON

The HTML body is no longer included in the default JSON output. If you need the full raw source, use --raw.

v0.2.0
v0.2.0

Agent Auth & New Homepage

Agents can now authenticate themselves — and we gave the whole site a fresh new look.

What’s New

Agent authentication

Agents can now handle their own auth flow end-to-end. Register an agent, claim it, and give it exactly the permissions it needs — no manual token juggling.

  • Agent registration: Walk through a step-by-step onboarding wizard to connect a new agent
  • Host management: Organise agents under hosts, view connection details, and track activity
  • Scoped permissions: Grant agents only what they need — mailbox access, domain verification, and more
  • Notifications: Get alerted when agents need attention or approvals are pending

New homepage

We redesigned the Broodnet website from the ground up — cleaner layout, better messaging, and a lot more personality.

v0.1.2
v0.1.2

Blog launch and app UI improvements

We launched a blog, and shipped a round of UI/UX improvements across the app dashboard — cleaner navigation, better spacing, and a more consistent layout throughout.

What’s New

App UI/UX improvements

A round of polish across the logged-in app experience:

  • Cleaner navigation and layout consistency throughout the dashboard
  • Improved spacing and visual hierarchy across all app sections
  • Better responsive behaviour on smaller viewports
  • Various small interaction fixes and accessibility improvements

Blog

The Broodnet Blog is live. Expect updates, tutorials, and research on email infrastructure for AI agents.

v0.1.1
v0.1.1

Custom Domains and CLI Improvements

Broodnet now supports custom domains for email sending and receiving, along with powerful new CLI commands for mailbox management.

What’s New

We keep improving the Broodnet experience with new features, improvements, and bug fixes. Here’s what’s new in this release:

Highlights

  • Custom domains: Add your own domain for sending and receiving email (Paid plan only)
  • CLI Improvements:
    • New broodnet mail status command shows live storage usage and mailbox status
    • broodnet mail config allows setting per-mailbox defaults like the default sender address
    • Improved email parsing and error handling across all mail commands
v0.1.0
v0.1.0

Initial Release

Broodnet is live. Provision real email inboxes for your AI agents in seconds.

What’s New

Welcome to Broodnet — email infrastructure built for AI agents. This initial release ships the core provisioning API, a basic dashboard, and IMAP-ready mailboxes.

Highlights

  • Mailbox provisioning: Create and manage real email inboxes via REST API
  • IMAP access: Each mailbox comes with token-based IMAP credentials for reading email
  • Dashboard: Manage all your mailboxes from a single view
  • Auth: Email and password authentication with secure session management
  • NO SPAM: Outbound email is only allowed between you and your agents, ensuring a safe environment.

Known Limitations

  • Single-organisation per account in this release
v0.0.0
v0.0.0

Hello World!

Hello World!

Hello World!

This is the first post in the Broodnet changelog. Here, we’ll share updates on new features, improvements, and bug fixes as we continue to build and refine our email infrastructure for AI agents.