I see what you mean. But maybe @Lorin_Thwaits’s comment kind of proves why the language might be confusing. exists? is pretty prevalent and to add a similar method that gives very different results could be confusing. I suspect that it would also be opening up a can of worms (multiple exists, nested exists) that might be more than you’re bargaining for. I’d prefer to hear the opinion of someone who’s actually contributed to this part of Rails, though.
Ah! Now I more clearly understand your goal, and realise that #active is likely a scope you’ve defined in the User model. If you’re okay to have the same kind of logic from that scope be instead in a .where then I can recommend: