Show HN: God Mode for Desktop Apps – Creator Browser
After installing Creator, you get a tiny 180KB application launcher proxy.exe. If your desktop app is app.exe, simply copy proxy.exe into the same folder as app.exe and rename it appProxy.exe.
Launch app.exe for normal mode; launch appProxy.exe to enter God Mode. proxy.exe launches app.exe as the Creator Browser’s Browser Process, then exits immediately, playing no further role. In God Mode, your application becomes an application content ecosystem interpreter: It can transform web pages, XML, or LLM content descriptions into dynamic interfaces. Native windows (such as Chromium browser windows, WinForm, MFC CView, etc.) are treated as tokens, dynamically composing the UI like a webpage.
No changes to the original code or recompilation are needed—your app instantly becomes a super composite UI generator.
We will be open-sourcing our complete Chromium M129 fork, with full build instructions, in the next 72 hours.
The brief delay is to ensure we provide you with a high-quality experience: we're finalizing the documentation, ensuring the build process is smooth and reliable, and preparing a guide that highlights the key modifications we made.
To get a head start, you can make sure you have the basic Chromium build environment set up: [链接到 Chromium 官方构建指南]
Watch or Star the repo to get notified the moment everything is live. We can't wait to see what you think and to answer your technical questions once you've had a chance to look through it!
Thank you for your patience – we want to make sure this is worth the wait.
The reason the core code is currently closed-source is that we are in the final stages of the patent review process for the underlying technology. This process typically takes about four months to complete.
We have always intended to open-source the project, and our plan is to release the source code under a permissive license (likely MIT or Apache 2.0) immediately upon patent grant. This approach protects the innovation during the review period while ensuring it becomes a public good afterwards.
In the meantime, we're using GitHub for its excellent tools for version management, automated builds, and community engagement (like this one!). We believe in being transparent about our build process and providing a public place for bug reports and discussions, even before the code itself is open.
We appreciate your understanding and are happy to answer any other questions!