This message was deleted.

Well, AS lags behind with the IJ version it uses as base, IJ lags behind with the AGP version it supports. ...

Well,

AS lags behind with the IJ version it uses as base,

IJ lags behind with the AGP version it supports.

...

true... I could check it chipmunk or dolphin behave better btw I wasn't able to google IntelliJ Android plugin roadmap/releases any page that would indicate which AGP versions are supported/expected to be supported by TK, does anyone know if there is such a thing?

If it works better, you can try using

buildSrc

instead of an included build (with exactly the same setup otherwise). Not super nice, but maybe an ok workaround for the time being. Then, when it is working in a future version, you can just rename

buildSrc

and include it. Anyway, thanks for filling the bug report. I think it It is very important to give this feedback. Enabling good tool support is the main reason why Kotlin DSL exists in the first place.

Then, when it is working in a future version, you can just rename 

buildSrc

  and include it.

Good point, haven't checked if buildSrc works any better. Anyway I'm fine having IJ open for gradle scripting and AS for everything else. We'll stick with using an explicitly includedBuild as we can then have it included only when working on the plugins and use a normal repository otherwise, which shaves off a few seconds of initialization/configuration time (at least according to few simple benchmarks)