Chrome supports an extension system  which generally functions as follows:
- Load a pre-packaged .crx file (zip archive) that contains the extension source code.
CEF will add support for Chrome extensions as a multi-step process:
The first round of implementation will include:
- Extension - The chrome.extension API has utilities that can be used by any extension page. It includes support for exchanging messages between an extension and its content scripts or between extensions, as described in detail in Message Passing.
- Runtime - Use the chrome.runtime API to retrieve the background page, return details about the manifest, and listen for and respond to events in the app or extension lifecycle. You can also use this API to convert the relative path of URLs to fully-qualified URLs.
- Storage - Use the chrome.storage API to store, retrieve, and track changes to user data.
- Tabs - Use the chrome.tabs API to interact with the browser's tab system. You can use this API to create, modify, and rearrange tabs in the browser. (For CEF this will operate on browser windows instead of "tabs".)
- Web Navigation - Use the chrome.webNavigation API to receive notifications about the status of navigation requests in-flight.
- Web Request - Use the chrome.webRequest API to observe and analyze traffic and to intercept, block, or modify requests in-flight.
- Windows - Use the chrome.windows API to interact with browser windows. You can use this API to create, modify, and rearrange windows in the browser. (For CEF this will operate on browser windows instead of "tabs".)
Other APIs under consideration for early implementation include:
- Browser Action - Use browser actions to put icons in the main Google Chrome toolbar, to the right of the address bar. In addition to its icon, a browser action can also have a tooltip, a badge, and a popup.
- Context Menus - Use the chrome.contextMenus API to add items to Google Chrome's context menu. You can choose what types of objects your context menu additions apply to, such as images, hyperlinks, and pages.
- DevTools - A DevTools extension adds functionality to the Chrome DevTools. It can add new UI panels and sidebars, interact with the inspected page, get information about network requests, and more.
- I18n - Use the chrome.i18n infrastructure to implement internationalization across your whole app or extension.
Any APIs that require user interface components, such as Browser Action, will be implemented as new CEF APIs that the client application will be responsible for implementing.
This is expected to be a long term project.