# AI is coming to Elements **URL:** \ **Category:** Announcements\ **Tags:** rapidweaver, elements, ai, devdiary\ **Created:** [June 11, 2026, 4:23pm UTC](https://forums.realmacsoftware.com/t/ai-is-coming-to-elements/56621 "2026-06-11T16:23:46Z")\ **Posts on this page:** 1\ **Showing post:** 38
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [June 12, 2026, 9:48am UTC](https://forums.realmacsoftware.com/t/ai-is-coming-to-elements/56621/38 "2026-06-12T09:48:33Z")
> [@Pegasus](#): > > I was just hoping that some of the issues that currently make the CMS 2.0 experience a little less smooth — for example: **The Load More issue** is something Ben can look into, we have a ticket for this and it’s scheduled for next week. **The OG URL is a bigger issue** , currently the CMS doesn’t know what Elements is outputting into the header as there’s no API for this. This is going to require us figuring out a nice solution so they can work more closely together. This will probably involve extending the Elements API. I have created a ticket internally for this, and it’s in the queue. I can’t say when this will make it into Elements, but it’s definitely on the radar and something I’d also like to see fixed. > [@Pegasus](#): > > I’m sure these things, along with many others, are already on your to-do list, and I can absolutely appreciate that you’re trying to balance a lot of different priorities and user requests. Yes, we have a detailed bug tracking system on GitHub so nothing is forgotten or missed. However, it most certainly is a constant balancing act between new features and bug fixes. Hopefully our past performance of constantly improving Elements is clear that we do eventually get round to fixing all the things! --- _[View the full topic](https://forums.realmacsoftware.com/t/ai-is-coming-to-elements/56621)._