Settings

Settings overview

Frost has eight settings across three pages. This is the quick reference; each page below goes into the detail.

Every setting

Setting	Page	Default	What it controls
SSO Start URL	Login	—	Your AWS access portal URL. Required.
AWS Region	Login	—	The region your IAM Identity Center instance lives in. Required.
Authentication Mode	Behavior	Auto-open browser	Whether a refresh may open the login page by itself, or notifies you first.
Login Page	Behavior	In-app window	Whether AWS sign-in opens in a Frost window or your default browser.
Refresh Hotkey	Behavior	`⌘⇧R` / `Ctrl+Shift+R`	Global shortcut that triggers a refresh, or opens a pending login.
Clear Cookies	Behavior	—	Throws away the in-app login window's cookies and local storage, so the next sign-in starts clean.
Retention period	Privacy	7 days	How long run history and log files are kept. 1, 3, 7, 14 or 30 days.
Delete History	Privacy	—	Erases all stored run history immediately.

Saving

Each configuration page has its own Save button and saves independently. Changes take effect immediately:

Login — saving discards the current token and starts a refresh with the new start URL and region.
Behavior — a new hotkey is registered on the spot; the mode and login page choices apply to the next refresh. Clear Cookies acts immediately and is not part of Save.
Privacy — a shortened retention period prunes history and sweeps old logs right away.

While you are editing a page, live updates from a running refresh cannot overwrite it — Frost leaves a form with unsaved changes alone until you save.

Things that are not settings

Some behaviour is deliberately fixed:

Start at login. Frost registers itself as a login item on every launch. Remove it through your operating system's startup items if you would rather it did not. Platforms →
Refresh interval. Frost refreshes when the current token expires; there is no interval to tune.
Which accounts are used. Frost writes a profile for everything the token can reach; there is no allow-list.
EKS scanning. The scan runs on every refresh and cannot be switched off. It only ever adds entries to your kubeconfig for clusters you can describe. EKS →
Log verbosity. Fixed at debug, which is what makes a failed sign-in diagnosable after the fact. Logs →

Where settings are stored

All of them live in Frost's configuration file, alongside the token and run history, written with owner-only permissions:

Platform	Path
macOS	`~/Library/Application Support/Frost/config.json`
Windows	`%AppData%\Frost\config.json`
Linux	`~/.config/Frost/config.json`

Deleting that file resets Frost completely: settings, token, discovered accounts and run history. It does not touch ~/.aws/config or ~/.kube/config — those keep whatever Frost last wrote. See files & locations.