How to Get Arc Browser's Command Palette in Safari

What Arc Got Right About Browser Navigation

Arc Browser, developed by The Browser Company, launched in 2022 and quickly became the browser of choice for a segment of power users, designers, and developers. It introduced several novel interface concepts, but the feature that generated the most discussion was its command palette: a searchable, keyboard-driven interface for controlling every aspect of the browser without touching the mouse.

Press Command+T in Arc, and instead of opening a blank new tab, you get a search bar that queries your open tabs, bookmarks, browsing history, and available actions simultaneously. Type a few characters, and the matching results appear in a ranked list. Press Enter, and you are there. No clicking through bookmark folders. No scanning a row of 30 tiny tab favicons. No opening the history menu and scrolling through pages of URLs.

This interaction pattern, borrowed from code editors like VS Code (Command+Shift+P) and productivity launchers like Alfred and Raycast (Command+Space), represents a fundamentally faster way to navigate information-dense environments. Instead of visually scanning, identifying, and clicking a target, you type a fragment of what you want and let the search algorithm find it. Studies on command palettes in code editors found that keyboard-driven navigation reduced average action completion time by 40-60% compared to menu-based navigation for experienced users.

The problem for many users is that Safari remains their preferred browser for other reasons: better integration with the Apple ecosystem, superior battery efficiency on macOS (Apple’s own benchmarks consistently show 1-3 hours more battery life compared to Chromium-based browsers), and native support for iCloud Keychain, Handoff, and Apple Pay. Switching to Arc for the command palette means giving up these advantages. The better approach is bringing the command palette to Safari.

How a Command Palette Changes Your Browsing Workflow

Before examining the implementation, it is worth understanding why a command palette matters. The core benefit is eliminating the visual search bottleneck.

The Problem with Visual Tab Management

A typical knowledge worker has 10-30 tabs open at any given time. Research from Carnegie Mellon University found that browser tab counts among office workers averaged 17, with power users regularly exceeding 40. At 10 tabs, the favicon and a few characters of the page title are visible in Safari’s tab bar. At 20 tabs, only the favicon is visible. At 30+, even the favicons start disappearing.

Finding a specific tab in this environment requires:

1. Visually scanning the tab bar (left to right, top to bottom in grid view)
2. Identifying the correct favicon or title fragment
3. Clicking the tab
4. If the tab is not visible, scrolling through the tab bar or opening Tab Overview

This process takes 3-8 seconds for 10-20 tabs and 8-15 seconds for 30+ tabs. It scales poorly.

The Command Palette Alternative

With a command palette:

1. Press the keyboard shortcut (typically Command+K or Command+Shift+Space)
2. Type 2-4 characters of the page title, URL, or content
3. The matching tab appears in the results list
4. Press Enter

This process takes 1-3 seconds regardless of how many tabs are open. It scales perfectly because search is O(1) from the user’s perspective, even though the underlying search is O(n). The user’s cognitive load is constant: remember a fragment of what you want, type it, confirm.

Beyond Tab Switching

A well-implemented command palette searches across multiple data sources simultaneously:

• Open tabs — find and switch to any open tab
• Bookmarks — access any bookmark without navigating folder hierarchies
• History — find previously visited pages by title or URL fragment
• Actions — execute browser actions like “Open Private Window,” “Show Downloads,” “Clear Cache”
• Extensions — trigger extension actions directly from the palette

This unification means you have a single keyboard shortcut for almost everything you do in the browser, replacing the need to memorize separate shortcuts for tab switching, bookmark access, history search, and browser settings.

Setting Up Command Palette in Safari

Command Palette for Safari brings this exact interaction model to Safari on both Mac and iOS. It provides a searchable overlay that indexes your open tabs, bookmarks, and browsing history, accessible via a single keyboard shortcut.

Command Palette — Arc-like Command Palette For Safari Download

Installation and Configuration

On Mac:

1. Install Command Palette from the Mac App Store.
2. Open Safari > Settings > Extensions and enable it.
3. Grant the extension appropriate permissions. For full functionality (searching across tabs and history), it needs broader access.
4. The default keyboard shortcut is typically activated via the extension’s toolbar icon on first use. Configure your preferred shortcut in the extension settings.

On iPhone and iPad:

1. Install from the App Store.
2. Enable in Settings > Apps > Safari > Extensions.
3. Access via the Safari toolbar or the extension’s designated activation method.

Configuring the Keyboard Shortcut

The keyboard shortcut is the single most important configuration choice. It needs to be:

• Fast to press — a two-key combination using the Command key is ideal
• Not in conflict — avoid shortcuts already used by Safari or macOS
• Memorable — Command+K (common in web apps for command palettes) is a natural choice

Common command palette shortcuts across applications:

• Command+K — Used by Slack, Notion, Linear, and many web apps
• Command+Shift+P — Used by VS Code
• Command+Space — Used by Spotlight (avoid this one to prevent conflicts)
• Command+E — Less commonly used, available in most contexts

First Use: Building the Index

When you first activate the command palette, it indexes your currently open tabs and accessible bookmarks. Depending on your bookmark library size, this initial indexing takes 1-5 seconds. Subsequent activations are near-instant because the index stays in memory and updates incrementally.

Keyboard-Driven Browsing Workflows

Workflow 1: The Instant Tab Switch

You have 25 tabs open. You need the GitHub pull request you were reviewing 20 minutes ago.

Without command palette: Open Tab Overview (pinch gesture on trackpad or click the grid icon), visually scan the thumbnail grid, identify the GitHub tab, click it. Time: 5-10 seconds.

With command palette: Command+K, type “github pr” or even just “pull”, press Enter on the matching result. Time: 2 seconds.

Workflow 2: Bookmark Access Without Folder Diving

You have a well-organized bookmark structure: Work > Projects > Client A > Design Resources. Accessing a specific bookmark requires four clicks through the folder hierarchy.

Without command palette: Click Bookmarks menu, navigate through three folder levels, find the bookmark, click it. Time: 5-8 seconds.

With command palette: Command+K, type the bookmark name or a keyword, press Enter. Time: 2 seconds. The folder structure is irrelevant. The command palette treats your entire bookmark library as a flat, searchable list.

Workflow 3: Re-Opening Recently Closed Tabs

You accidentally closed a tab or closed one you now need again.

Without command palette: History > Recently Closed, scan the list, click the correct entry. Or Command+Z to undo the close, which only works immediately after closing.

With command palette: Command+K, type part of the page title, and the history results include recently visited pages. The distinction between “open tab” and “recently closed” disappears; you just search for what you want.

Workflow 4: Quick Actions

Need to open a private browsing window, manage downloads, or access Safari preferences?

Without command palette: Navigate through the Safari menu bar, find the correct menu, find the correct item, click it.

With command palette: Command+K, type “private” or “downloads” or “preferences,” press Enter on the matching action. Browser actions become as accessible as document content.

Workflow 5: Research Mode

When researching a topic, you open multiple tabs from search results and cycle between them rapidly.

Without command palette: Click between tabs in the tab bar, losing track of which tabs contain which subtopics, frequently overshooting the target tab.

With command palette: Keep your hands on the keyboard. Command+K, type a keyword related to the specific aspect you want to review, switch to that tab. The keyboard shortcut becomes your navigational hub, and you develop a rhythm: read, Command+K, type, Enter, read.

Power User Customization

Building Quick-Access Shortcuts

Some users create bookmarks specifically for command palette access rather than traditional bookmarking. Naming bookmarks with short, unique prefixes makes them instantly accessible:

• Bookmark named “gg - Gmail” matches on typing “gg”
• Bookmark named “jira - Project Board” matches on typing “jira”
• Bookmark named “cal - Google Calendar” matches on typing “cal”

This effectively creates custom short aliases for frequently visited sites, similar to Chrome’s custom search engines but more flexible because the palette searches across all data sources.

Combining with Safari’s Native Shortcuts

The command palette does not replace Safari’s existing keyboard shortcuts. It complements them. The most efficient keyboard-driven browsing combines both:

The command palette handles the “I know what I want but not where it is” scenarios. Native shortcuts handle the “I know exactly what action I want to perform” scenarios. Together, they cover nearly every navigation need without the mouse.

Why Command Palettes Work: The Cognitive Science

The effectiveness of command palettes is grounded in how human memory and attention work.

Recognition vs. Recall. Navigating menus uses recognition: you see options and recognize the one you want. Typing into a command palette uses recall: you remember a fragment of what you want. Cognitive psychology research shows that recognition is easier than recall, which might suggest menus should be better. But there is a critical factor: as the number of options grows, recognition-based scanning becomes slower because each option must be visually processed. Recall-based search stays fast because typing 3-4 characters is constant-time work regardless of how many items exist.

Motor efficiency. Keyboard input is faster than mouse input for experienced typists. Moving a hand from keyboard to mouse, positioning the cursor, and clicking takes 1-2 seconds. Typing 4 characters takes 0.3-0.5 seconds. For actions performed dozens of times per day, this difference compounds.

Reduced decision fatigue. Menu navigation requires making multiple sequential decisions (which menu, which submenu, which item). Command palette use requires one decision (what am I looking for?) followed by confirmation. Fewer decisions means less cognitive drain over a workday.

Beyond Arc: The Command Palette as a Universal Pattern

The command palette pattern is rapidly becoming the standard for navigating complex interfaces. Spotlight was an early consumer implementation. VS Code popularized it for developers. Figma, Notion, Linear, Slack, and dozens of other productivity tools have adopted it. Apple’s own Shortcuts app uses a searchable action library that follows the same principles.

In the browser specifically, the command palette is the natural evolution from the “awesome bar” concept that Firefox pioneered and Chrome refined, where the address bar serves as both a URL field and a search interface. A command palette extends this concept to include not just web searches and URL navigation but also tab management, bookmark access, history search, and browser action execution.

For Safari users who want to browse as efficiently as Arc users without leaving the Apple ecosystem, a command palette extension is the single highest-impact productivity addition you can make. For a broader look at productivity-focused Safari extensions, check our guide on the best note-taking and productivity Safari extensions.

Start by using it exclusively for tab switching for one week. Once that becomes muscle memory, expand to bookmark access. Then history. Then actions. Layering one capability at a time prevents the cognitive overload that comes from trying to change every habit simultaneously. Within a month, reaching for the mouse to navigate your browser will feel like an unnecessary detour.