Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Everyday tasks

LobeHub 2.3.3 gives agents an inbox

Written November 13, 2026

LobeHub 2.3.3 adds an agent inbox and reply rules. What arrives there, and what the rules let an agent answer on its own.

What changed

LobeHub 2.3.3, released November 12, 2026, gives every agent an identity of its own: an address, an inbox, and a Profile page. The release covers 253 merged pull requests and 252 commits from 12 contributors since 2.3.2, and its own summary names the theme: direct Channels with their own reply rules, an inbox identity for every agent, and projects that can be created straight from a repository.

The shift is in how an agent is reached. Instead of existing only inside a chat you start, an agent in 2.3.3 can receive mail, sit in group conversations, and decide for itself whether a message is its business. The pieces below are the ones that change day-to-day use.

Channels, and each agent's own reply rules

Every agent and group now has a direct Channel: an IM-style conversation surface with stacked header avatars, a typing indicator in the header, a card composer, day dividers, and reply activity shown on list rows. Channels sort in the sidebar with unread and mention highlights, and threads now open as the page rather than in a side panel.

On top of the Channels sits a per-agent reply strategy. Each agent decides when to wake:

The inbox

Agents get an address and an inbox, with a Profile page under an Identity group in their settings. Mail is a wake source like any other: when mail wakes an agent, the run posts what it concluded back to the owner's Channel. An agent only ever sees its own mailbox, and the release's security notes repeat the point from the other side — a mail-woken run is scoped to its own mailbox. Workflow callbacks now fail closed when unauthenticated, as part of the same hardening pass.

What arrives in the inbox is whatever is sent to the agent's address. What the agent may answer on its own is bounded by the same reply strategy as the Channels: its rules first, silence on follow-ups that are not its concern, and one primary responder for unaddressed mail. The release notes do not describe the inbox as a general email client for the user; it belongs to the agent.

Also in 2.3.3

Limits

Related playbooks

Sources

Back to: Everyday tasks playbooks hub · Also: Copilot joins Slack and Teams for real