Instance appearance

Give browser instances recognizable labels and badge colors through Extended Preferences.

Entitlement: instanceAppearance. Configuration: internal.instance_appearance. No JavaScript call is required to display the badge.

Configure

Merge into Extended Preferences, sign if required, and launch:

{
  "internal": {
    "instance_appearance": {
      "label": "Workspace 01",
      "background_color": "#059669",
      "foreground_color": "#FFFFFF"
    }
  }
}

Field	Requirement/default
`label`	Non-empty string; absent or empty disables the appearance configuration
`background_color`	`#RRGGBB`; default `#2563EB`
`foreground_color`	`#RRGGBB`; default `#FFFFFF`

Invalid colors fall back to defaults. Short hex notation, alpha channels, and CSS color names are not accepted. Use a short label because the title-bar badge has a bounded width.

What it affects

The label and colors identify an instance through Chrovia's title-bar badge and application-icon integrations on Windows and macOS. Windows also integrates profile shortcut icons. These appearance features, including the title-bar badge, are not implemented on Linux.

This is per-instance appearance, not compile-time product branding. It does not rename the executable, application bundle, Provision directory, or every page title. Those are different configuration surfaces.

Verify

On Windows or macOS, launch two separate user-data directories with different labels and compare their badges. If absent, check the License, non-empty label, EP location and signature. Restart after changes. To read the configured label from a plugin, chrovia.prefs.get('internal.instance_appearance.label') separately requires extendedPrefs.

For application metadata independent of visual appearance, use instance metadata.