🧩 Cleaner and more customizable building experience

Announcements New Releases
1

We’ve redesigned the editor layout to give you more control and a cleaner workspace, so you can build the way that works best for you.

Whether you’re using AI, editing visually, or switching between both:

1920Ă—1094 222 KB

Separate spaces for visual editing & AI generation

The Edit panel and WeWeb AI chat are now in separate spaces, making the editor easier to navigate and less cluttered:

• Open or hide the Edit panel independently

• Open or hide the AI chat independently:

Faster navigation & layout controls

The new layout also helps you adapt the workspace to your workflow:

• Quickly access the AI chat and Preview directly from the navigation bar

• Customize your workspace depending on how you like to build

• Switch more easily between building, reviewing, and previewing your app

As always, let us know what you think :slightly_smiling_face:

2

omg! Huge thanks for the two things:

  1. Preview button doesn’t migrate anymore between frames
  2. Debug panel now stays pinned in “preview” mode

Those issues were pretty uncomfortable :slight_smile:

I was going to bring them up at the upcoming meeting with Raphael, but the update beat me to it :slight_smile:

3

Glad to hear that you like it! :slightly_smiling_face:

4

I don’t know if it’s just me, but since the update I can’t open any of the options inside workflows, for example, I can’t disable a node or change the formula of a field inside the workflow. Tried opening in safe mode but didn’t helped either.

5

hey I was about to post here about the exact same problem.

Guys, I love that you’re pushing updates on the daily, but maybe you should consider some “beta feature” opt-in to let your users decide when they want their editor to be updated. Right now it’s like changing mid-session and with bugs that could be avoided if I could simply stay on the previous version of the editor until the new release is confirmed stable.

6

Have the same issue. Not everywhere, but some bindings just doesn’t open inside workflows

7

same problem here and I 100% agree with Axel it is a bit annoying. Thankfully I dont have a hotfix to do.

8

Agree. It’s nice all the effort weweb team it’s putting into the platform, and I happily test as beta, but is annoying to get surprised with changes mid-session, dealing with bugs and being unable to do something about it.

9

Hey everyone,

Thanks for reporting this!

The team is aware of the issue, and they working on a fix.

10

Hello everyone,

We just pushed a fix. It should be all good!

Please let us know if you still have any other issue. Sorry again for that issue

11

Works. Thanks for your reactivity !

12

Captura de tela 2026-05-21 195205
Captura de tela 2026-05-21 195205326Ă—270 10.3 KB

I’m running into a recurring issue with the AI Chat (Build and Ask mode).

Any prompt I send — even the simplest ones, visual-only and with no bindings — fails after ~3s with the same generic message:

“Run failed — [layout name] could not be applied because of an internal system error.”

Nothing is applied partially and the error gives no clue. It happens both with prompts that use collections/formulas and with 100% hardcoded layouts, so it doesn’t look like a data source issue on my side.

Any solution?

13

Thank you for moving the preview button! That was getting unbearable the amount of times I had the go back dropdown block it.

Just one thing that’s changed that is a bit of a weird decision in my opinion. The preview button is now always blue, for people that have been on weweb for awhile this can completely mess with us. Cause I’m so used to blue being in preview mode. Can’t we keep the in edit mode grey and in preview mode blue? I really don’t understand this change, there was nothing wrong with it before.

14

I am still dissatisfied with WeWeb Unify but these changes make things a bit smoother.

15

Haha yes! It messes with my brain as well. I don’t know if it’s a legacy thing and the UX is actually better for new users and we will prefer it once we get used to it. In any case, I’ve shared the feedback with the product team so they can explore further

16

Yes, there’s still some work to do! We’ll keep working on improving the UX of the new editor

17

I haven’t come across this. If you haven’t already, would you mind creating a support ticket here with some info to help us reproduce the issue?