CHANGELOG · RELEASE 23 · 20th June 2026
Every spec comes back in your real files.
9 signals from your GitHub repository, so nobody has to translate the spec.
A spec that guesses your file paths is a spec somebody has to translate. The builder reads it, works out where it really goes, renames half of it, and starts. That translation step is the work Annsa exists to remove.
Connect GitHub and every spec comes back in your real files, your real naming, your conventions. Hand it to Cursor or Claude Code and the build starts on the first read.
The specs you already have re-ground the moment you connect. There is nothing to regenerate by hand.
Needs a connected GitHub repo.
How to use it
A spec that guesses your file paths is a spec somebody has to translate. The builder reads it, works out where it really goes, renames half of it, and starts. That translation step is the work Annsa exists to remove. Connect GitHub and every spec comes back in your real files, your real naming, your conventions. Hand it to Cursor or Claude Code and the build starts on the first read. The specs you already have re-ground the moment you connect. There is nothing to regenerate by hand.
- Settings, then Connect, then GitHub. Pick the repo.
- Existing specs re-ground on their own.
- Hand any spec to Cursor or Claude Code. It names real files.
Also in this release
Spec numbers
Every spec carries a short number in the panel, the export and annsa.spec. Say Spec #14 and everyone knows.
annsa.help
Ask how scoring works from Cursor or Claude Code and get the answer without leaving your build.
Rank and context cards
See what drives a priority and the customers behind it as two cards. Both travel into the export.
Improvements
Fixed. Ask drew on customers it could not see. The free-tier rollover did not run on schedule. The default project counted against your plan.
