- Less waiting in Teams. History imports write messages in batches rather than repeatedly rewriting each transcript file.
- Tidy project families. Fold a parent project’s running tasks into one row while leaving its sub-projects visible.
- Quicker routine replies. Ordinary Slack replies skip checks that only matter for messages needing requester attribution.
Slack and Teams
- Lighter history imports. Teams groups transcript updates by file, cutting repeated work while keeping the same messages and ordering.
- Quicker ordinary replies. Slack sends that do not need requester attribution no longer wait for its audience checks.
Web app
- Tasks in one row. A parent project's running tasks start folded behind an N tasks row, with the fold remembered per project, on web and desktop.
- Link to a helper run. Open a project's helper run directly from a link on web and desktop, using the project's existing access rules.
Admin and billing
- Faster comparisons and name lookups. Usage does less competing work while loading chart comparisons, and Teams usage pages can look up several group-chat member lists at once.


