Application settings

Gotchas and known limits

• Two save models on one form: theme, checklist and voice input apply instantly and ignore Save; the rest is dropped silently if you navigate away before Save (filling git-user-name-input, then clicking sidebar-settings-/settings/secrets and back, shows the stored openhands again; browser dialogs is empty). Assert the instant ones without clicking Save, and never expect Save to enable for them.
• The success toast uses the language that was active when you clicked Save, not the one you saved. In F16.language the French Save toasts Settings saved, the Arabic Save toasts Paramètres enregistrés, and the English restore toasts تم حفظ الإعدادات, so wait-text 'Settings saved' times out on the last two. Assert with browser text 'testid=submit-button' after a reload, or read the toast with browser toasts.
• Some chrome strings stay English after a language switch: the sidebar Automate label in every language (the automation interface supplies it, not the translation file), and most of the command menu's own texts (placeholder Search actions, pages, and settings..., the search box's Search commands name, the group names and the item names) in French and 11 other languages. Only the Model Router and Agent Context items are translated (Routeur de modèles and Contexte de l'agent in French), because they reuse the settings navigation's titles. Do not treat the English ones as a language switch failure; the sidebar trigger's Search commands is translated.
• In Arabic (dir="rtl") a switch that is on draws its thumb outside its track (on show-getting-started-checklist-switch the track spans x 778–818 and the thumb 822–838). Assert switch state with .checked, not from a screenshot.
• The switches are hidden checkboxes: browser click 'testid=enable-analytics-switch' times out (element is not visible). Click the label text scoped to testid=app-settings-screen, and read .checked through eval.
• role=option[name^=...] is not supported by the selector parser; use role=option >> has-text=<profile> for profile options whose names include the model.
• conversation start leaves the browser on the conversation page, which also has a testid=submit-button; goto /settings/app before the next settings step or clicks hit the composer.
• Which profile actually generated a title is not visible in the UI, the conversation API or the stack logs; F16.title-model proves the preference is stored and a title appears, not which model wrote it.
• onboard --skip stores analytics off, so a fresh run starts with the switch unchecked even though the code defaults to on when the preference is missing.
• browser storage lists localStorage, and browser storage --session lists sessionStorage, where the voice-input key lives. With --values that key prints as <redacted>, so the recipe reads its dummy value with eval. The key disappears in a new tab or browser session by design.
• Deleting a profile through the LLM settings UI clears a matching title preference itself; only a profile removed outside the UI leaves a stale title_llm_profile that this page shows as Automatic.
• The Title generation model combobox has a clear (×) button with no accessible name (- button in the snapshot, visible as × at phone width). At desktop width it only takes clicks after browser hover on the input (F16.title-model-clear); otherwise use the Automatic option.
• browser eval wraps its argument as an expression: statements separated by ; fail with SyntaxError: Unexpected token ';'; wrap them in (() => { ...; return x; })().
• With service stop agent-server, a browser reload of /settings/app shows the backend-unavailable screen (agent-server-onboarding-screen, Manage backends), not the form: stop the service only after the page is loaded, and restart afterwards.
• Known product bugs (repro candidates): git identity never reaches the agent (#17899); switches are not keyboard reachable or announced (#17900); a failed save discards the user's edits (F16.save-states) (#17927).
• The harness builds with VITE_DO_NOT_TRACK=1, so PostHog never starts: browser network --filter 'posthog|z\.openhands\.dev' reports total 0, also after analytics consent is granted (#18086). A browser-only Do Not Track setting, and a non-DNT build where consent starts PostHog, cannot be driven with the harness (F16.analytics).
• The title model's clear button has no test id: the recipe's xpath relies on DOM nesting to skip the unnamed Show suggestions button. If both ever match, Playwright's strict mode fails the click instead of pressing the wrong one; report it as harness drift.