Changelog for 2026

A year of releases is easier to read in one place than in twelve release notes, so this is the whole of 2026 in one page: what changed, why we changed it, and what it means for the way you work. Nothing here is a breaking change — every item landed behind a flag first and stayed there until the numbers looked right.

The composer got faster and quieter

The composer was the first thing we rebuilt. The old one re-rendered the whole draft on every keystroke, which was fine for a short post and noticeably slow for a thread of fifteen. The new one keeps each channel variant in its own document and only reconciles when you switch tabs, so typing stays at one frame per keystroke no matter how many channels are connected.

Two smaller changes came along with it. Drafts now autosave on a debounce rather than on a timer, which means the “unsaved” indicator finally tells the truth. And the character counter understands per-channel rules, so a post that is fine on one network and too long on another shows the warning where the problem actually is.

Reporting moved from daily to hourly

Engagement data used to land in a nightly batch. It now arrives hourly for every channel that supports it, and the dashboard shows the collection time next to each figure so nobody has to guess how fresh a number is.

Alongside that, the rollup finally does what most teams were doing by hand: it groups posts by campaign, sums the reach, and reports click-through against the campaign’s own destination rather than against whatever link happened to be in the post. Exports include the raw rows, so a spreadsheet-shaped team can keep working the way it prefers.

The automation canvas

Automations used to be a list of rules. They are now a canvas: a trigger, optional filters, and one or more actions, drawn as a graph you can follow with your eyes. Every run keeps a trace, and a failed run can be replayed against the current version of the flow without re-triggering the original event.

The most requested addition was a scheduled trigger, which shipped in March. The second most requested was the ability to pause a flow without deleting it — that shipped the same week, mostly because it turned out to be four lines of code once the canvas existed.

Approvals, comments and history

Review used to happen in chat. It now happens on the draft: comments anchor to a specific channel variant, approvals are recorded with the approver and the timestamp, and every revision is kept. If a post needs to be reconstructed after the fact — which happens more often than anyone expects — the history tab has it.

Teams on the Pro plan can require an approval before anything is queued. That setting is per workspace, not per user, so it cannot be quietly turned off by whoever is in a hurry.

Smaller things worth knowing

The connection library grew by four channels. Keyboard shortcuts now cover the whole calendar, including moving a post between slots with the arrow keys. Time zones are stored per workspace instead of per user, which fixed a long-standing class of “why did this go out at 3am” bugs. And the mobile layout of the calendar was rewritten from scratch; it is the change we hear about most.

What is next

The 2027 roadmap starts with two things: a proper content library so assets stop living in a shared drive, and a permissions model with more than three roles. Both are already in design, and both will land behind a flag like everything else here.

If something on this list changed a workflow you had built around the old behaviour, tell us — the migration notes are written from the questions we actually get, not the ones we imagine.