CHANGELOG · 17th September 2026
Everyone behind the priority hears what shipped.
Share back reaches every customer whose feedback is on the priority, in words you edit, and their reply lands on the work.
Share back reaches every customer whose feedback sits on a priority, including the people who arrived after the spec was written, and what they say back lands on the work they answered.
Closing the loop is the step that slips. The people who reported a problem are spread across months of feedback, the note has to be written for them rather than from a build log, and once it is sent there is rarely a way to see what came back.
Annsa draws the recipients from the priority itself at the moment you send. The message is written from the customer's own words, and you can edit all of it, headline included, before it goes. A priority reads as shared only when someone was told. A reply lands on the priority it answers, and a customer who changes their mind sees the answer they already gave.
How to use it
The people who told you about a problem are the reason it got built. Share back keeps that list on the priority itself, so the note reaches everyone on it at the moment you send rather than a list captured when the spec was written.
- Open Share Back and choose a shipped priority.
- Read the draft. It is written from the customer's own words, and you can edit all of it, headline included.
- Send it, then watch the replies land on the priority they answer.
Also in this release
New feedback lands on the right priority
Annsa shortlists the priorities a new piece of feedback could belong to and judges each one, so 4 people describing the same problem in different words become one priority and unrelated feedback stays apart.
Cut a release from everything you shipped
One release holds every spec shipped since the last one, numbered in order, so a period of work reads as one thing instead of a list of tickets.
Answer your agent's question without leaving your terminal
When an agent needs a decision it raises the question, and your answer lands on the priority and the spec together.
See where every piece of feedback landed
The reply to a submission names the priority it joined, or the nearest one and its score when it stands alone, and a row that matched nothing carries the reason it is waiting.
Specs read in the words a customer would use
A priority and its spec say what becomes true for the customer, and carry the decision behind the work and what was ruled out straight through from the person who made it.
Improvements
- Share back
- Share Back works through every shipped priority in one scrolling panel over the spec. The whole email is yours to edit before it goes, headline included. A priority reads as shared once someone has been told, and an agent sharing over MCP hears how many people it reached. The reply page shows a customer the answer they already gave, and lets them change it.
- Priorities and placement
- Feedback stays where you or your agent puts it, and a row you move teaches Annsa where that kind of feedback belongs. Every placement names the rule that placed it. Merging a priority carries its feedback to the survivor, and when 2 priorities look like the same thing Annsa raises it for you to decide. Bets are optional: a list with no bets ranks and triages just as well.
- Specs
- An edit in the sheet records who changed which section. A shipped spec stays as it shipped. The decision behind a priority and the options it set aside read the same in the sheet and in what an agent is given, and each passage appears once on the page.
- Coding agents
- Codex and Cursor can claim, note and verify work. Every action has one name, and the reply names it. What an agent learns while shipping stays on the priority. A route given an MCP token names the kind of token it expects and where that token is accepted.
- Board and roadmap
- A saved view's name is the page heading. A roadmap card is its title and one row of facts. A new bet shows on the board the moment you create it, and triage says what each row needs from you and opens it on the row.
- Limits and delivery
- Feedback held over your plan limit returns exactly as you sent it, keeping its kind. A priority shows when its change reached your main branch and is live for customers, and the sheet marks a pull request merged the moment it merges. Settings refetches your product's own words and says what it found.