Send feedback
Three flavors of feedback, three different best routes. All on GitHub — public, threadable, and tracked.
Bug report
Something broken, weird, or doesn't match what the docs say? Opens a pre-filled GitHub issue with a short template (what happened, expected, browser, song slug). Public so others can pile on if they see the same thing.
Open bug template →Feature request
Have an idea, an itch you'd like scratched, or a workflow that should exist? Opens a pre-filled GitHub issue describing what you want, why, and how big it feels. Every one gets read — even the ones that don't end up shipping.
Open feature template →General feedback / thoughts
Bigger-picture thoughts, what worked vs. what felt clunky, research collaboration, anything that doesn't fit a single issue. Open a GitHub Discussion — public, threadable, easier to find than email.
Start a discussion →What helps me triage fast
For bugs:
- A song slug if it’s reproducible on a specific song — that pins down the audio you were looking at.
- Your annotator namespace (the email you sign in with) — useful for inspecting the exact state your annotations are in.
- A screenshot or a short clip if it’s visual — much faster than describing a layout glitch in words.
For features:
- The workflow you’re trying to do matters more than the specific button you wish existed. Often there’s a simpler way to land what you want than the feature you first sketched.
- How often this comes up — once-a-month annoyances and every-session frictions need very different cost/benefit math.
Status of past requests
The GitHub issue tracker is the canonical place to see what’s open, what’s in flight, and what’s shipped. Closed issues link to the commit that resolved them.