Google is moving ahead with a new compose box experience for Chrome’s New Tab Page.
A new Chromium code change, submitted on June 10 and spotted by Techdows, enables the “NTP composebox fork” by default, which means Chrome is now preparing to use the newer compose box implementation on the New Tab Page.
Google updated the kUseNtpComposeboxFork feature parameter from false to true in Chrome’s compose box field trial configuration. This means the new version of the compose box is no longer disabled by default inside Chromium.
The compose box is part of Google’s work around the New Tab Page, where Chrome can surface search or AI-powered input experiences more directly.
While the code change does not fully explain what the new implementation looks like, the wording confirms that Google is activating a forked version of the compose box by default.
Chrome’s New Tab Page is getting a new compose box implementation
The Chromium change is titled “[ntp-composebox] Enable NTP composebox fork by default.”
NTP stands for New Tab Page, and “composebox” likely refers to the input box that appears on the page. Google already uses the New Tab Page for search, shortcuts, Discover-like modules in some regions, and other Chrome features.
With this change, Chrome is preparing to switch to a newer compose box implementation by default. The exact visual changes are not visible from the code alone, but the commit message says the change “activates the new composebox implementation on the New Tab Page by default.”
That confirms this is not just an internal cleanup. It is a feature configuration change that decides which compose box Chrome should use.
Google changed the default value from false to true.
