Related: when edebug is active, any buffer with lispy active will forward to edebug, i.e. if the point is at |(some-func) in a common lisp buffer and I type f, then special-lispy-flow is called and rather than calling lispy-flow in my common lisp buffer, it calls edebug-forward-sexp in whatever buffer edebug is running in.

I think lispy--edebug-commandp should check that edebug-mode (which is buffer-local) evals to t, since edebug-active is not buffer local. That change fixed the problem for me.