Arc
ComponentsBlocksDocsPricingTry the demo
Introduction
Installation
Theming
Motion
AI and MCP
Changelog
Metrics dashboard
KPI drilldownNew
Metric explorer
Revenue explorer
MRR waterfall
Cohort retention
Usage forecast
Journey flow
Connected scatterNew
Market terminalNew
Budget varianceNew
Small multiplesNew
Line replayNew
AI chatNew
AI composer
Agent runNew
SidebarPro4
Page header
Command palette
Notification center
Empty states
Login and sign up5
OTP input
Multi-step formPro
Settings page
Settings commandNew
Security settings
Billing overview
Usage billingNew
Cancel flow
Team members
Invite peopleNew
Team directory
Roles and permissions
API keys
Webhooks
Integrations
Plan comparison
Pricing calculatorNewPro
Usage pricingPro
Cart drawerNewPro
Checkout summaryNewPro
Invoice studio
Wallet card
Product listingNew
Product detailNew
Inbox triage
Support conversation
Support widget
File upload
Media playerPro
Week calendarNew
Availability picker
Project board
Release readiness
Hero sectionNew
Hero signupNewPro
Scroll storyNewPro
Spotlight gridNewPro
Feature bentoNewPro
Comparison tableNew
Logo marquee
Studio perspectivesPro
Stats bandNew
Changelog feed
FAQ sectionNew
Contact sectionNew
Team showcasePro
Blog gridNew
Site headerNew
Site footerNew
CTA sectionNew
Newsletter signupNew
Activity terrain
Revenue globe
Customer galaxy
Semantic zoom
Layout morph
What’s new83 new
BlocksSettings command

Settings commandPro

Workspace settings where a search field grows into a palette that flies you to any setting.

Live block · sample data

When to use

  • Workspace or account settings with several sections and many options.
  • Admin consoles where support links people to a specific setting.
  • Any settings page where people ask where something lives.

When not to use

  • Use settings-page for a short, paged profile form with a few fields per section.
  • Use command-palette for app wide navigation and actions, not just settings.
  • Avoid it for a single form; a plain form with a submit button is clearer.

Installation

Pro source and install commands unlock with a Pro plan.

Usage

Use this for app or workspace settings with many options. Describe your settings in the data file, load saved values from your API, and persist the changed ids through onSave; saving in the preview is simulated.

example.tsx
1import { SettingsCommand } from "@/components/arc/blocks/settings-command/settings-command";2import { settingDefinitions, settingsSections } from "@/components/arc/blocks/settings-command/settings-command-data";3 4export function WorkspaceSettings({ saved }: { saved: Record<string, string | boolean> }) {5  return (6    <SettingsCommand7      sections={settingsSections}8      settings={settingDefinitions}9      defaultValues={saved}10      onSave={async (values, changed) => {11        await fetch("/api/workspace/settings", { method: "PATCH", body: JSON.stringify(Object.fromEntries(changed.map(id => [id, values[id]]))) });12      }}13    />14  );15}
Built fromSwitchSegmented controlAnimated counterText morphButton

API reference

SettingsCommand

Workspace settings on one scrolling page with a sticky section nav, a search field that grows into a command palette, and an unsaved changes bar. Picking a result flies the palette into the matching row, scrolls it into view, and the row breathes twice.

PropTypeDefaultDescription
sectionsSettingsSection[]settingsSectionsSections in page order: id, label, and a one line description.
settingsSettingDefinition[]settingDefinitionsEvery setting: id, section, label, description, kind (switch, segmented, select, text), options, keywords for search, placeholder, and prefix.
defaultValuesRecord<string, string | boolean>savedSettingsSaved values keyed by setting id. Edits are compared against these to count unsaved changes.
suggestedstring[]suggestedSettingIdsSetting ids listed in the palette before anything is typed.
onSave(values, changedIds) => Promise<void> | void–Persists the draft. Resolve to confirm; reject to keep the bar open with Retry. Without it the save is simulated.
onValuesChange(values) => void–Called on every edit with the full draft.
titlestring"Settings"Heading beside the search field.
classNamestring–Class on the root.

Keyboard interactions

Command KorControl Korslash
Opens the settings search while focus is inside the block.
Arrow uporArrow down
Moves through results. The input keeps focus; the active result is announced through aria-activedescendant.
Enter
Jumps to the active result and moves focus to its control.
Escape
Closes the palette back into the search field and returns focus to it.
Tab
Moves through section nav, controls, and the Save and Discard buttons.

Accessibility

  • The palette is a modal dialog with a combobox input and a listbox of options; the scrim closes it on press.
  • Each row labels its control with the setting label and describes it with the hint and any validation error.
  • Edited rows and sections carry a dot plus visually hidden Edited text, so the state never relies on color.
  • A polite status region announces jumps, saves, discards, and validation problems.
  • Invalid fields block saving; Save jumps to the first invalid row the same way search does.

Motion

  • The search field grows into the palette: position, size, and corner radius ride one spring, and results are revealed by the growing edge instead of reflowing.
  • Picking a result flies the palette into the target row while the page scrolls, then the row's wash swells and settles twice.
  • The section nav highlight glides to whichever section is in view as you scroll.
  • The unsaved changes bar grows out of a small puck, rolls its count, and shrinks into Settings saved.
  • Reduced motion swaps flights for fades, scrolls instantly, and keeps a single soft pulse.

Responsive behavior

  • Below 720px the section nav becomes a scrolling row above the content.
  • Below 480px select and segmented rows stack their control under the label; switches stay inline.
  • The palette always fits the frame with a 12px margin and drops its hint row on phones.

Performance

  • Search is a synchronous filter over the settings array; it stays instant for a few hundred settings.
  • Scroll spy is throttled to one read per animation frame.
  • The palette and save bar animate transform, size, and opacity of a single element each.

Notes for AI

Give your coding assistant the Markdown reference instead of screenshots.

  • Choose it when a product has more than about 15 settings and people search for them by name.
  • Add keywords for the words people actually type, such as 2fa, sso, dark mode, or invoice.
  • Keep the data file as the single schema: the palette, nav, and rows all read from it.
  • Send only the changed ids to your API through onSave and reject on failure so the bar offers Retry.
/components/blocks/settings-command/markdown

The full library index for assistants is at /llms.txt.

Related

Settings pageProBlockAccount settings with a gliding section nav and a save bar that morphs in as you edit.Command paletteBlockA complete keyboard driven action surface with search, grouped results, and shortcuts.Security settingsProBlockAn account security page with guided two-factor setup, password change and active sessions.SwitchComponentA tactile toggle for settings that take effect immediately.Segmented controlComponentSwitch between a small set of related views.
PreviousContact sectionNextUsage billing
Arc · 78 block pagesllms.txt

On this page

  • Preview
  • When to use
  • When not to use
  • Installation
  • Usage
  • API reference
  • Keyboard
  • Accessibility
  • Motion
  • Responsive behavior
  • Performance
  • Notes for AI
  • Related
View as Markdown

Settings

General

Name, address, and regional defaults for Northwind Studio.

Shown in the sidebar, invites, and emails.

Changing it breaks old links for 30 days.

arc.so/

Used for dates, numbers, and interface text.

Due dates and digests follow this zone.

Affects calendars and weekly reports.

Appearance

How the app looks for you on this device.

Match the system or pick one.

Compact fits more rows in lists and tables.

Scales text across the app.

Show unread counts beside each view.

Turn off to swap movement for fades.

Notifications

Choose what reaches you and how often.

When someone @mentions you or your team.

New issues and reviews that land on you.

Builds that fail on a branch you own.

A Monday summary of what shipped.

Batch emails to cut down on noise.

Security

Sign in rules and session policy for everyone.

Everyone adds an authenticator app or key.

Members sign in through Okta only.

Idle people are signed out after this.

Only office and VPN addresses can sign in.

How long sign ins and changes are kept.

Members

Who can join and what new people can do.

Given to everyone who joins by invite link.

Admins approve requests from everyone else.

Guests see only projects shared with them.

People with these addresses join without an invite.

Billing

Where invoices go and how they are issued.

Receipts and payment alerts go here.

Applies from the next billing period.

Email admins at 80% of the monthly budget.

Printed on every invoice.