Framer, please bring back these two workflow features

I've been using Framer extensively for client work, and there are two changes to the editor that have made my workflow noticeably more cumbersome.

Neither of these is really a request for "new" functionality. Both are things Framer previously allowed us to do, and I'd really like to see that functionality restored.

I've included screenshots showing the areas I'm referring to.

When editing a page, Framer used to have a clickable link at the top of the canvas that opened the current page's live URL in a new tab.

It was simple, contextual, and incredibly useful.

That functionality isn't completely gone, but accessing it now requires several steps:

Menu → Settings → Find the page → Open the page → Click the live URL

The problem gets worse as a project grows. If a project has dozens of pages, I first have to locate the page I'm already editing among a long list of paths.

If I'm currently editing /services/web-design, Framer already knows that I'm editing /services/web-design.

Why shouldn't I be able to simply click a link at the top of the canvas and open that page?

This is one of those small UX decisions that doesn't seem significant until you perform it dozens of times a day.

Please bring the clickable live URL back to the page canvas.

This one has had an even bigger impact on my workflow.

Previously, page-specific custom code could be accessed directly through that page's Settings, while global/site-wide code was managed separately.

That made the context very clear:

Page → Settings → Custom Code

If I needed to modify code belonging to a particular page, I went to that page and edited its code.

The new Custom Code system centralizes everything into the main Custom Code area.

I understand the appeal of centralizing code management. But the tradeoff is that I now have to go into a large collection of code entries and find the one associated with the page I'm working on.

For a small project, that's probably not a huge deal.

For projects with lots of pages and custom code, it becomes a significant maintenance problem.

I'd like to see both approaches coexist.

Keep the centralized Custom Code interface.

But also bring Custom Code back into individual page Settings.

Ideally:

Global code remains available in the central Custom Code area.

Page-specific code remains available in the central Custom Code area.

Individual page Settings provide direct access to that page's code.

Editing the code from either location updates the same underlying code.

That gives us the organizational benefits of the centralized system without sacrificing contextual access.

While we're talking about the new Custom Code system, there's another workflow issue I'd love to see addressed.

I can manually arrange my code entries in the order I want, which is useful.

However, when I add custom code to a new page, the new entry is simply added to the bottom.

So I have to manually move it into the appropriate location every time.

I'd love to have persistent sorting/grouping options such as:

Alphabetical

Page/path

Global vs. page-specific

Custom/manual ordering

Groups/folders

Or simply a persistent sorting preference

Even a basic "sort by page/path" option would make a huge difference for larger projects.

Why I'm pushing on this

These might look like relatively minor UI requests individually.

They're not minor when you're managing a large number of client pages.

I use Framer as part of a larger client workflow, and I'm frequently jumping between pages, checking live versions, modifying page-specific code, and making relatively small client changes.

When a workflow that used to take one click becomes several clicks—and that process is repeated across dozens or hundreds of pages—the accumulated time becomes significant.

More importantly, I'm currently evaluating the long-term platform decision for this workflow.

I've been weighing Framer against Webflow. One of the things that makes Webflow increasingly attractive for my particular use case is that I can have a custom application programmatically update and publish a project.

With Framer, I'm already having to manually make and publish relatively small page changes for clients.

So when editor changes make those manual workflows more cumbersome rather than less, it starts to affect the bigger platform decision.

I like Framer. That's why I'm asking for these things rather than simply moving on.

But I do think there's a larger point here:

When a platform removes small workflow optimizations that professional users rely on, those changes can have a much larger impact than they appear to from the perspective of an individual feature.

I'd really like to see these capabilities restored—or see equally efficient alternatives introduced.

My three requests:

I'd be very interested to hear whether other Framer users are experiencing the same workflow issues, particularly anyone managing larger client projects.

Framer has a lot going for it. I'd rather see these workflows get better than find myself having to move an entire platform workflow back to Webflow.