(Also, same for "extensions" – but you can "open" apps in a way you don't "open" extensions.)

From internal G+ where I commented on this:

"Not what you're asking for, but: we used to have an omnibox apps provider that could surface the actual apps you installed, directly from the omnibox, by name.  We removed it because the times it did trigger actively annoyed users -- they didn't expect or want the omnibox to do that, and the app names often overlapped with common search/nav entries and thus interfered.

"Now, to your request: we do have a "builtins provider" that can surface chrome://apps if you type it from the beginning (i.e. "chrome://ap...").  It can handle about: pages as well.  The most direct way of doing what you want would be to extend the matching on this provider so it's token-based instead of prefix-based, much like the HistoryQuickProvider.  Whether that's worth doing I don't know; I'm not sure this is a use case many other people run into.  But if you want to file a bug for that, I'm not opposed."

Or we can add chrome:// URLs to history, a la  bug 23110 , so that if a user visits a particular URL often, it'll be surfaced by the omnibox (HistoryQuick provider) and given a reasonable ranking compared to other pages.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot