Bloomfire vs Tana

Tana has spent the visible window building around the meeting rather than the note. The 28 August release turns the voice agent from an input method into a background worker: several requests run at once while the conversation continues, it acts in connected tools, and it reads the day's agenda, pinned items, captured outcomes and the shared screen for context. Around that sit a natural-language search that resolves plain questions into filter pills, a saveable search document, and a long tail of meeting-surface refinements.

The through-line since July is Tana claiming the meeting itself — first as the default place to hold the call, then as the system that notices unscheduled ones, and now as an agent doing work during them. Each release has moved further from recording what happened toward acting while it happens. The supporting work is consolidating too: one transcript, one digest timeline, one filter bar, which is the housekeeping that follows a surface being used seriously.

Expect the concurrent agent to be given more tools to act in and the daily brief to grow beyond Slack, since both are described as user-editable rather than fixed. The open question these entries do not settle is how Tana handles an agent that edits documents mid-meeting when it gets one wrong.