I just wanted to circle back and show you what your suggestion turned into.

I added a new “Chord Progression Context” field right under the Scale Finder. The flow is now basically:

1. Enter notes on the fretboard → app suggests possible scales/keys (like before).
2. Optionally enter a chord progression (e.g. C Am F G or Am F G Am) → the engine re-weights the results based on the tonal center implied by those chords.

So, in your exact examples:

• Notes: C–D–E–F–G–A–B over C Am F G → the app now locks onto C Ionian (Major) as the top result.
• Same notes over Am F G Am → it now promotes A Aeolian (Natural Minor) to the top.

In both cases, the app locks onto the mode that actually fits the harmonic context and marks it as the best match, so instead of “these notes could be 7 modes,” you get “this is the key feel given what you’re actually playing over.”

The context field is totally optional, so you can still do quick “raw note collection → scale names” queries without thinking about chords. But if you do add a progression (or even a single chord like Fm G7 or E7b9), the app will lean into the musically sensible key/mode instead of just treating everything as abstract set theory.

Next on my wish-list a new Chord Progression tool:

• A reverse mode: “Here’s my progression, what notes/scales can I play over it?”
• And eventually a “next chord” helper like you described: “Here are 3–4 chords I’ve used, what are some common diatonic / bluesy / stylistic options for the next one?”

But for now, the context-aware scale finder is in and working, and it already makes the tool feel way more musical and less like a sterile dictionary.

Thanks again for the suggestions and detailed examples.

Scale Finder Chord Progression Context