Click Ask Annsa in the top-right header. It opens as a floating panel, so you don't lose your place.
01Open it
02Ask about your feedback
"What are customers saying about the checkout flow?" · "How many people mentioned performance this month?" · "What's the most common complaint from enterprise customers?"
03Ask about priorities and specs
"What's our highest-priority bug right now?" · "What's been parked and why?" · "What does the spec for dark mode say to build?" · "Show me the Done When criteria for the CSV import spec."
04Ask about your own history
"What did we ship last quarter?" · "Which customer segment drives most of our feature requests?" · "Have we shipped anything related to notifications before?"
05Narrow it to an area
Name the area in the question — "what's the top complaint about billing?" — and Annsa narrows to the priorities and feedback covering that topic. Same pool, narrower question.
06Long answers arrive whole
A long question comes back finished rather than however far Annsa got before it stopped — the answer you take into a roadmap call reads as an answer, not a fragment.
07How the answers are built
Retrieval-augmented search across your feedback, priorities, specs and activity log. It finds real content in your workspace rather than generating from scratch, and streams the response as it works.
08It reads, it doesn't write
Ask Annsa won't create or edit priorities, regenerate or restatus specs, send notifications, submit or delete feedback, or take action in GitHub, Slack or Linear. For actions, use the MCP tools from your editor.
09Ask Annsa or MCP?
| Ask Annsa | MCP tools |
|---|---|
| In-app, browser-based | In your editor (Cursor, Claude Code) |
| Natural language Q&A | Structured tool calls |
| Explore and understand | Act and implement |
| Great for research | Great for building |
10Tell it when it's wrong
Thumbs up or down after a response feeds back into answer quality.