WeWeb AI now provides clearer plans and task tracking, helping you understand what it’s about to build and follow its progress as it works.
We’ve also improved MCP support.
Check out the details 👇
📄 Clearer planning and task tracking in WeWeb AI
Follow progress with task tracking
WeWeb AI now shows a task list while working on larger requests, making it easier to understand what it is doing and how far along it is.
You will see a progress card showing the tasks it plans to complete, how many are done, and which ones are still in progress:
This helps you:
- Understand the steps behind a larger request
- See progress without waiting for the final result
- Quickly spot what has already been completed
Improved planning
Plans are now clearer, more structured, and easier to review in a dedicated Plan mode:
A plan now includes:
- A summary of what WeWeb AI intends to do
- Technical details for the proposed implementation
- A clearer overview of what may be created or updated in your app
After reviewing the plan, you can approve it or continue chatting to refine it.
Once approved, WeWeb AI switches to Build mode and uses the approved plan as context to complete the work.
Other WeWeb AI improvements and fixes
WeWeb AI now better follows best practices and respects your existing project setup.
This includes improvements to:
- Using, creating, and updating design system tokens more reliably
- Reusing existing sections when relevant
- Choosing native WeWeb components instead of recreating them from scratch
- Respecting existing icon libraries
- Handling hover and active states more consistently
- Applying styling choices more predictably, including colors and existing element styles
- Setting the app’s default theme when the app design is light or dark
- Generating cleaner, more beginner-friendly JavaScript with helpful comments
🖇️ MCP improvements
The team made a series of improvements to MCP support, including:
- MCP sessions no longer drop
- MCP now uses tokens from design system by default
- MCP now setups debounce by default when building inputs
- Fixed issues that could happen when creating dynamic links
- MCP now uses the native WeWeb Calendar element by default
- MCP now leverages reusable sections when building multi-page apps
- MCP now properly uses the hover state instead of adding state logic through a workflow
- Fixed issues where MCP was struggling with API endpoints related to tables using paramaters
- Improved readability of MCP outputs in workflows with instructions to write more beginner-friendly JS code and comments
That's all for now! As always, let us know what you think 🙂
