I usually just evaluate *e for this purpose.

There is Print Last Exception command as well

Thanks! Those are useful. What I am looking for though is to have this shown in the IntelliJ debugger and be able to navigate the stack, inspect local variables in each frame etc like in the screenshot. Is this possible? If not, can I extract the same information from this *e object somehow?

I think you can use this feature: https://www.jetbrains.com/help/idea/analyzing-external-stacktraces.html

I’m not sure you can analyze the runtime state of a stack trace in an Exceptuon though…

I guess what I am after is functionality like this one from PyCharm. This happens automatically whenever an exception is raised and I am in debug mode.

That looks like Exception Breakpoints: https://www.jetbrains.com/help/idea/using-breakpoints.html#exception-breakpoints

Great! This is what I was looking for.

Still have to figure out how to use this well. If I configure this to show me "caught" exceptions as well, there is an unusable amount of noise. But if I set it to only show me "uncaught" exceptions, it won't trigger when I evaluate forms in the REPL. So apparently I have to set appropriate "catch class filters" in this dialog. I have gotten as far as figuring out that the pattern clojure.lang.* is what makes the difference - but unfortunately it affects both the noise as well as the exceptions that bubble up to the REPL. Any advice for how to capture exactly those exceptions that "would be caught in such a manner so that a stack trace is printed on the repl" would be super useful.

The dialog I was referring to:

after some experimentation, best setting I found for the REPL use-case is to set the "catch class filter" to the class clojure.lang.Compiler