You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary: This update includes quite a lot of content, especially in design bug fixes and minor feature optimizations. The following only highlights the key updates. In general, we've optimized the software and added some new features.
Note: If you discover new bugs, please feel free to submit issues. If you're interested in this project, we'd appreciate a star — it helps more people discover it.
Future: This project will always be free, but we may consider adding some ads in the future. However, they won't affect the user experience — no ads on the main interface, and definitely no shake-to-open ads.
Added "Disable Memory Preloading" option — When enabled, non-essential content is no longer preloaded; actual impact is relatively minor.
🧹 Code & Architecture
Removed a large amount of redundant code — Cleaned up legacy implementations to reduce maintenance costs.
Completely removed the legacy editing mode — All related code has been deleted and is no longer available.
Refactored node configuration file storage format — The new format is more efficient but may carry stability risks; backward compatibility with the old format is supported. It is recommended to use the old format in production environments for now.
🖥️ UI/UX Refactoring
Mobile AI/MCP interface refactored — New layout, along with fixes for multiple interaction issues.
PC settings page refactored — Redesigned layout and interaction logic.
Fixed an issue on mobile where clicking "Load Configuration" or related options had no response.
Fixed an issue on mobile where the cropping box could not be used for cropping.
Attempted to fix an underlying issue where GPU rendering failed on some mobile devices (still needs verification on certain models).
Fixed untranslated queue processing strings (now all displayed in Chinese).
⚠️ Known Risks
The new node configuration file format is not yet stable. It is recommended to continue using the old format and wait for a stable release before migrating.