Specialty is Less Important Than Mastering the Craft of Code
It sounds like what you care about is job prospects in general. For that, you want to focus on what the comp. sci doesn't teach you, which is the craft of writing code well. Having subject matter to focus on that interests you as you self-teach is the most important thing, IMO. That said, choosing AI will suggest you enjoy a challenging problem which is something most of us like to see in a prospect so I'd say you can't go wrong with AI if the ultimate goal is just to establish a career as a programmer.
Self-Teach What They Can't
So don't sweat the specialization. Most general application developers only care about your ability to generally handle any problem and whether you can write lean, mean, maintainable code. Just be prepared to self-teach on those more pragmatic aspects as you go.
On that front I would focus on learning to appreciate more general principles first and to always put them first when evaluating what sorts of methodologies/patterns/etc. you want to use. For instance a lot of devs glom on to complex design patterns before they understand the value of basic fundamentals OOP first which leads to them doing silly things like implementing complex stuff that could have been much more elegantly handled by language features.
Take What They Teach About the Craft With a Grain of Salt
Profs teaching comp sci might have a lot of valuable skills to impart but still aren't necessarily exemplars when it comes to learning how to write code professionally so learn to develop your own opinions even if you have to accommodate their style preferences for the A. For instance, KISS and DRY are typically the first casualty of over-solving the problem but they NEVER should be. It's almost always easier to go back to a simple solution and expand on it to accommodate new, more complex needs, than it is to solve a problem you don't have yet and then maintain and build on that needless complexity often at a geometric-ish rate moving forward. I've seen countless Java and C# code that doesn't understand this. Write code like a good martial artist uses strength. No more and no less than exactly what was needed. (I'm not a martial artist so maybe that's some BS I heard somewhere but hopefully the point is clear)
Try to come out of school with at least three at-least somewhat popular but dissimilar languages in your pocket and advanced knowledge of at least the one that you like working with the most. Make sure at least one doesn't have c-based syntax. Understanding languages as a series of design tradeoffs is invaluable and only having functional literacy in one language tends to be a stigma, at least to web developers.
Consider Demand AND Supply
Shameless Prod Towards Own Language Preference/Hint: Since you like AI, it seems likely to me that you'll be picking up some lisp-variant. (I'd be dubious of a school that stuck with Java or C# for AI). JS is much-inspired by Scheme and strong JS devs aren't easy to find. Not to mention JS has its hands in just about everything short of embedded apps nowadays.
There's Only One Way to do it Right
People fond of saying this tend to dislike considering every way before they decide on a preference. It should always smell like snake-oil when expressed in this manner. That said, we're all guilty of it from time to time. I just got my chops rightfully busted for such a statement on SO today in fact.