Changelog

Read team analytics over the REST API

Four endpoints report on one team: action-item follow-through, carry-forward, participation, and feature adoption. Every number is an aggregate, and no response names a person. Each endpoint uses the API scope that matches the data it returns.

Ask an MCP agent how the team is doing

The get_team_analytics tool returns the same four aggregates in one call, so an agent that summarises a team does not need four requests. The tool returns only the parts your token has scope for, and it names the parts it leaves out.

The audit log records votes

The audit log now records each vote that a person casts and each vote that a person removes. An entry about a post, an action item, or a group also carries the retro it belongs to, so an export tells you where the entry came from.

The team retro list keeps a stable order

Two retros created in the same moment could swap places between page loads. The list now has a total order and does not reshuffle.

The app stops retrying a retro link that is not valid

Open a link to a retro that does not exist, and the app now says so and stops. Before, it reconnected in a loop. The app also counts every failed attempt, including a connection that drops at once, so it gives up instead of retrying forever.