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:
- Its own rules come first.
- Follow-ups stay silent.
- Unaddressed messages get one primary responder, rather than every agent answering at once.
- The runtime records why a wake happened, so a reply that surprises you has a reason attached to it.
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
- Projects from GitHub. Create a project from a repository, pick its work location, edit or remove working directories, and link tasks to projects with a picker, badges and grouping. New projects default to a dedicated main agent, and code projects run in the sandbox inside the project's own repository.
- Desktop serves the remote terminal. The desktop app can serve a remote terminal to the web and mobile clients, alongside local-file preview for remote devices.
- Other harnesses, steered. Claude Code sessions can be steered with queued follow-ups, OpenCode 2.x is supported, and Copilot and Cursor ACP run with full access by default.
- Behind flags. A Lobe Bench workspace (benchmarks, datasets, experiments), a meeting data model with an API, and versioned skill archives arrive behind flags rather than as general features.
- Reliability work. Page collaboration keeps one document tree per page with durable rooms, context snapshots are pooled so long runs stop growing traces, and file parsing no longer blocks the event loop.
Limits
- The inbox and reply rules are described in release notes, not in a user guide with worked examples; how a rule is written is a settings question the notes do not walk through.
- The Bench workspace, meeting model and skill archives are flag-gated in this release, so most users will not see them yet.
- Copilot and Cursor ACP running with full access by default is a setting to notice before you point either at a repository you care about.
Related playbooks
- Sort and summarise a messy inbox into next actions
- Get a ranked shortlist of remote jobs in your inbox every day
- Perplexity Teammates: always-on agents, $200 a month
- Cheapest way into an always-on agent
Sources
Back to: Everyday tasks playbooks hub · Also: Copilot joins Slack and Teams for real