A recent build of Chromium, the open source project behind Google Chrome, added support for user scripts. For now, the support is limited: Chromium reads the scripts from the hard-coded directory c:\scripts and it ignores the @include metadata which restricts scripts to one or more web addresses. To enable Greasemonkey support, you need to use the flag: --enable-greasemonkey, for example by appending it to the target of a shortcut.
I tested the Greasemonkey support with the old script Linkifier, which turns text URLs and email addresses into links.
The new feature has been contributed by Aaron Boodman, the creator of the Greasemonkey extension for Firefox, who happens to work at Google.
In September, Google's Sundar Pichai said that Chrome will have an API for extensions. "We don't have that in the beta today, but we definitely plan an extension API. It is one of the things we will get to next." It seems that Google Chrome will provide native support for Greasemonkey scripts before releasing the API.
* to get early access to developer-oriented Google Chrome builds, subscribe to the Dev Channel and read the release notes.
* the latest Chromium snapshots are available at the BuildBot site, but they don't support Google's auto-updater and they're less stable than the official releases. You only need to download the file chrome-win32.zip from the most recent folder.
2 hours ago