Project email went from a message list you could send from to a mailbox you can work out of.
Threads, not messages
Mail is grouped into conversations. A thread opens as a stack of messages with sender avatars, recipient details you can expand, and quoted history collapsed out of the way until you want it — so a twelve-message chain reads as one thing instead of twelve rows competing for attention.
Project mail also syncs in the background rather than only when you open the page, so the mailbox is current when you get there.
A faster mailbox
Thread listing was rebuilt to stop fetching message bodies it never renders. Large project mailboxes open noticeably faster, and scrolling a long thread list no longer waits on the server between pages.
Helix drafts, you review
Ask Helix to reply to a thread or write a new mail and the draft appears inline in the conversation — recipients, subject, and body laid out the way they will send. You can edit it in place, open it in the full compose pane, or discard it. Nothing leaves the mailbox until you send it.
Replies and forwards keep the thread’s participants, subject, and quoted history without you rebuilding any of it by hand.
Also in this release
- When a project has no Gmail integration connected, the mailbox now says so and points at where to connect it, instead of rendering as an empty inbox.
create_bugno longer returns a 500 for JSON requests — filing a bug from an MCP client or the API works with or without an attachment.- Project search keeps matching projects visible after you apply a filter, rather than clearing the result you just searched for.