Not sure it's idiomatic, but the inline def trick can be helpful for that. (def this-particular-thing this).

that one works, there's also a hashmap of component instances in the app itself: https://book.fulcrologic.com/#_fulcro_application_whats_in_there see ::indexes

If you use(d) https://fulcro-community.github.io/guides/tutorial-minimalist-fulcro/ I'd interested in hearing how it worked for you 🙏 I use repl a lot but rarely need 'this'. For transact! you can simply use the 'app'. What else do you need it for? There is also something like comp/class->any and similar to get the instance of a component

This is also super-handy: https://github.com/vvvvalvalval/scope-capture I use it more in clj than cljs, but it works for both. Then of course if you're using shadow-cljs and just need to explore some data in a component, you can use tap>.

@U0522TWDA I’m still trying to grok how everything fits together, so being able to use stuff like comp/get-query in context would be helpful for me.

get-query takes class not an instance so you do not need this for that

My https://www.eventbrite.com/e/reclojure-introduction-to-fulcro-workshop-tickets-188718210247 on Dec 1st could be perhaps useful to you. If you cannot make it, you can try to do it on your own, following the https://github.com/holyjak/fulcro-intro-wshop/blob/main/docs/Workshop.adoc. This will teach you a lot about the browser and REPL tooling that we used when making and troubleshooting Fulcro apps.