When we’re in one of our new-builder-built apps, using our lovely custom domain, e.g.
customdomain.com/rr/app/example
and we tap the “Edit app” button, it loads the builder in our retool subdomain, e.g. oursubdomain.retool.com//rr/edit/letters-and-numbers
This often compels us to have re-login because of the domain change, when we’re already logged in via our custom domain. Not the end of the world, but still 
Here’s the part that surprised me – the editor can be (re)loaded just fine by swapping the oursubdomain.retool.com with customdomain.com in the URL
Since the editor functions exactly the same via the custom domain, shouldn’t/couldn’t the “Edit app” button be custom-domain aware, and load the editor under the custom domain?
After a little more nosing around, I discovered that from our Retool home page (our list of apps and app folders with “edit” and “view” buttons), when loaded via our custom domain, the edit buttons on that page all load the editors under our custom domain. So those Edit buttons are custom-domain-aware, yet the Edit app button on the apps themselves, are not? 
Summary
On Retool Cloud with the new app builder, opening a published app via a custom domain (e.g. Checking your browser...) and clicking the in-app "Edit app" button loads the editor on the org's retool.com subdomain instead of the custom domain, which often forces a re-login — even though the editor works identically under the custom domain and the Edit buttons on the home/apps list page are already custom-domain-aware.
AI Response
This behavior reflects a current inconsistency in how the new app builder generates the in-app "Edit app" link versus the home page Edit buttons, rather than a technical limitation, since the editor loads correctly when the subdomain is manually swapped for the custom domain. A reliable interim workaround is to edit the URL directly — replace oursubdomain.retool.com with customdomain.com in the /rr/edit/... path to stay on the custom domain and avoid the re-login. There is no published documentation or existing forum report that specifically covers the in-app Edit app button not being custom-domain-aware, so no directly relevant solution or corroborating report was found. The most closely related public materials confirm that new-builder apps on custom domains are supported and that domain redirection preferences have been a recurring request.
Sources
Publishing apps on custom domains
Official product update confirming new app builder apps can be published on custom domains, establishing the expected custom-domain behavior for these apps.
Request: Auto-redirect from org.retool.com to custom domain
A related standing request to have Retool consistently route/redirect from the org.retool.com subdomain to the custom domain, which parallels the desired custom-domain-aware Edit app behavior.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a
,
, or
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. 