Settings reference: options, defaults, and when they apply
Look up settings by section and understand saved values, installation defaults, scope, and experimental options.
Settings & helpHow to use this reference#
Open Settings from the sidebar and find the relevant section below. Tables explain each option and when it takes effect. For worked examples, see settings and data.
Your displayed value takes precedence. Upgrades generally preserve existing choices. The tables distinguish new-install defaults from fallback values used when a saved configuration is missing a field.
General and Appearance: preferences and display#
General
Open General for language, window behavior, new-session permissions, external applications, notifications, and updates. Display controls live in the separate Appearance section.
| Option | How to choose | Effect and scope |
|---|---|---|
| Language | Choose the interface language | Not a universal response-language switch |
| Always on Top | Keep results visible while using other apps | Applies to the window immediately |
| Default Permission Mode | Default, Auto, or Full Access; see permissions | New-session default; sessions can override |
| Default open tool | Choose a detected editor or remember the last tool | Controls the external-editor button's main action |
| In-app notifications | Show completion notices inside Onevium | Independent of desktop notifications |
| Desktop notifications | Receive alerts outside the window | Requires OS permission; Do Not Disturb can suppress them |
| Keep running in background | Prevent automatic sleep during active work | Uses more power; does not guarantee macOS lid-closed operation |
| Check for Updates | Inspect version and available updates | Download or view the release as offered; verify after restart |
Session organization → Naming rules
AI naming is opt-in. Open Settings → Session organization → Naming rules and enable Automatically update conversation titles only if you want it. Choose the naming model and inspect the saved prompt; changes save automatically. Enabling it does not immediately rename old conversations. Manual titles remain protected, and naming runs under the eligibility conditions shown in this section. Existing saved naming policies are retained; a missing policy defaults to off. Manual Generate with AI remains a separate action when automatic naming is off.
Appearance → Theme and typography
| Option | How to choose | Effect and scope |
|---|---|---|
| Light / Dark / System | Fix the brightness or follow the operating system | Applies across the workspace; saves automatically |
| Workspace palette | Neutral, Warm paper, Codex style, GitHub style, Notion style, Claude style, Catppuccin, or Nord | Eight palettes, each with light and dark colors; changing palette also selects its matching link color |
| Link and focus color | Palette default, Blue, Teal, Plum, or Warm brown | Colors conversation links and keyboard focus outlines |
| Visual contrast | Standard or Higher contrast | Makes muted text and boundaries more distinct |
| Interface / Message / Code font | Choose each font category separately | Separate fonts for interface text, conversation text, and conversation code blocks |
| Chat text size | 12–16px | Adjusts conversation text; inspect the live preview |
| Message weight | Regular or Medium | Adjusts body text; headings and bold retain emphasis, and code weight is unchanged |
| Code text size | 10–16px | Adjusts conversation code blocks separately from message text |
The built-in terminal and code editor follow the workspace colors; changing a workspace palette does not configure an external editor.
Choices save automatically and apply to all conversations. If saving fails, the last saved appearance is restored and Retry is available. Restore color and font defaults resets those appearance choices while keeping reading density and the Light/Dark/System selection.
Appearance → Sidebar and session list
Open Settings → Appearance → Sidebar and session list. For example, choose the status-right preset, then check that conversation titles remain readable while activity states move to the right.
| Option | How to use it | What to verify |
|---|---|---|
| Layout preset and individual positions | Start with all-left, status-right, or all-right; adjust markers, channel/schedule icons, and activity status independently | Check the preview and an existing conversation |
| Sidebar text size | Adjust navigation, project names, and session titles | Message and code text sizes remain independent |
| Initial default width | Enter at least 260 px, then leave the field or press Enter | A manually dragged sidebar width remains the remembered choice |
| Channel conversation titles | Show or hide sender and group/contact names separately | With both enabled, the sender comes first; these labels do not change the connected account |
| Navigation entries | Show, hide, or reorder entries | Hidden entries remain under Explore; New session stays first |
You can also right-click the navigation menu and choose Customize, or open Customize from Explore, to change entries in place. Finish editing and reopen Explore to confirm a hidden entry is still reachable. Sidebar presentation changes save as you adjust them; check any save error before assuming a change persisted.
Appearance → Conversation display
| Option | How to choose | Effect and scope |
|---|---|---|
| Reading density | Compact, Standard, or Relaxed | Adjusts message spacing and line height across conversations; Restore spacing default resets only density |
| Default Chat Process View | Full for debugging; hidden for reading results | Saves the display default while preserving individual conversation choices; tools still run |
| Message Navigator | Return to earlier messages in long chats | On by default; hover at the chat's edge |
| External editor entry | Show the toolbar action for opening the project | Hidden by default; choose its default application in General |
| Commit entry | Show the toolbar commit action | Hidden by default; Review can still commit |
Appearance → Motion and performance
| Option | How to choose | Effect and scope |
|---|---|---|
| Reduce visual effects | First adjustment for flicker or stutter | Reduces decorative animation immediately |
| Disable hardware acceleration | Try if reducing effects does not help | Requires restart; may reduce smoothness |
Installation defaults and saved choices
Some defaults differ between fresh installations and older configurations:
| Option | Fresh-install baseline | Missing-value fallback in older configurations |
|---|---|---|
| Theme / language | Light / Chinese | Existing choice or environment initialization |
| Permissions | Full Access | Default, or compatible existing full-access configuration |
| In-app / desktop notifications | Off / on | On / off |
| Automatic AI naming | Off | Off without an explicit naming policy; saved choices remain in effect |
| AI browser control | Off | Existing enabled settings, including earlier migration defaults, remain enabled |
| Background activity | On | Off |
Choose the default model through provider and conversation model controls. Default reasoning effort is in the provider's model configuration, described below. General has no independent Enter-to-send preference.
Providers: model connections#
Add or adjust providers, models, and connection configuration here. Confirm the endpoint, credentials, and model, then send a short message. Saving does not prove a working model. See providers and custom providers for the fields.
Open the relevant provider's model configuration and expand Default reasoning effort. Choose a starting level for a model that supports multiple levels. Each choice saves immediately for that provider and model, including when the surrounding model dialog has separate Save/Cancel controls. The default seeds new conversations; existing conversations retain their own effort choice. Create a new conversation with that provider and model to verify it. Models without multiple supported levels do not appear in this list.
For an Anthropic-compatible relay, open the provider editor → Advanced Options → Endpoint supports 1M context. Enable it only after the service confirms support, and also enable the global 1M Context Window option in Claude Code settings. This endpoint assertion appears for Anthropic/custom provider types, not every protocol. It does not enlarge an unsupported model's context window. Save the provider and verify a new conversation with the intended model.
Claude Code: shared CLI configuration and advanced options#
| Control | Purpose | Saving, scope, or limitation |
|---|---|---|
| Extended Thinking | Adjust extended reasoning on supported models | Saves immediately; model support varies |
| 1M Context Window | Enable a long-context option for supported Anthropic models | Experimental; account and model eligibility still apply |
| Agent Teams | Enable experimental CLI teams | Separate from Onevium's newer @Team workflow |
| Teammate Mode | auto, in-process, and platform-dependent tmux/iterm2 | Shown when teams are enabled; affects Claude in a terminal, not automatic in-app selection |
| Permission Rules | Edit CLI permission JSON | Valid JSON plus Save; a different layer from the session selector |
| Advanced → Environment Variables | Change variables passed to Claude | Edit JSON, save, and confirm; retain unrelated fields |
| Advanced → other fields | Edit existing advanced configuration | Keep unfamiliar fields unchanged; Reset discards unsaved edits |
| Edit Raw JSON | Edit the whole configuration | Format, review, and save; may affect CLI using the same settings |
An unchecked CLI boolean does not describe every model's underlying defaults. Verify changes in a new conversation. Configuration can contain credentials; remove them before sharing screenshots.
Network proxy: routing and validation#
| Control | What to enter or choose | Effect and check |
|---|---|---|
| Mode | Off, App Only, Global; normally Off without configuration | App Only is for Onevium; Global changes system proxy settings |
| Proxy Type | HTTP, HTTPS, or SOCKS5 as supplied | The proxy protocol, not the destination site's protocol |
| Server Address / Port | Separate host and port fields | Enter a hostname and port number; leave fields to save |
| Username / Password | Only when the proxy requires authentication | Password is saved separately and can be cleared |
| Extra Direct Addresses | Additional domains or hosts that should bypass the proxy | Local addresses already bypass it |
| System Proxy Status | Applied or Not Applied in Global mode | Check this, not just the selected mode |
| Test Proxy Server | Save parameters and select Test | Scope explained below |
| Check Browser Exit IP | Open the check page in Global mode | Verify the browser's exit separately |
Test scope: the Test action creates a proxy tunnel to ifconfig.me:443, then attempts /ip. An established tunnel can return success even when IP retrieval fails. If an IP is shown, it describes that test request's exit.
This does not test Anthropic or a custom model endpoint, validate a model account, or prove a separate browser uses the same route. Verify model access with a real conversation separately.
Switching away from Global attempts to restore the previous system proxy. Windows and Linux SOCKS have system-authentication limitations; other apps may request credentials separately or omit them.
Original proxy settings with isolated example values. No system proxy change or test was performed. This version tests an IP echo service, not the model account.
Activity: local usage and cost observations#
| Control | What it shows | Useful approach |
|---|---|---|
| Year and heatmap dimension | Messages, sessions, tokens; defaults to current year and messages | Compare the same year and dimension |
| Time range | Today, yesterday, 7/30/90 days; defaults to 7 days | Narrow the range to investigate a spike |
| Provider filter | All or one provider | Identify which connection contributes usage |
| Include cache | Whether chart data includes cached tokens | Off for that chart layer by default; compare like with like |
| Cost, tokens, cache hit rate | Local records and price estimates | Notice unknown-price exclusions and pricing dates |
Estimated cost, cache savings, and an official invoice are different. This section also differs from subscription limits below.
Tools: built-in capability groups#
| Group | Purpose | Default or behavior |
|---|---|---|
| Schedules | Manage automations | Opt-in; enable in Settings → Tools or through the relevant capability activation card |
| Widget | Create visual artifacts | On by default |
| Recap | Generate work recaps | Opt-in; enable in Settings → Tools or through the relevant capability activation card |
| Services | Manage services | On by default |
| Channels | Let the assistant manage channel configuration | Off by default; not the switch for connected bots |
| Sessions | Work across conversations and organize titles | Opt-in; enable in Settings → Tools or through the relevant capability activation card |
| Browser | Browser tools when available | Also requires AI browser control in Settings → Browser |
| Continuity / channel runtime | Automatically supplied runtime tools | Informational rows, not switches, in the current interface |
Schedules, Sessions, Recap, and Channels require an explicit saved on setting; a missing setting is off. Already enabled settings are retained. Turning these tool groups off does not delete existing conversations, schedules, or recap data, and is not a control for cancelling an existing schedule.
Disabling a group prevents further calls; newly enabled tools are available with the next message. Switches do not undo completed actions or stop an active task. Tool counts and token estimates need not match fixed numbers in a tutorial.
Personalization and memory#
| Control | Purpose and when to change it | Default, scope, and effect |
|---|---|---|
| AI Autonomy master switch | Controls related autonomous processing | On by default; user rules also depend on it |
| User Rules | Stable preferences and habits | Off by default; up to 4,000 characters; autosaved; user scope |
| Memory extraction | Extract durable information from conversations | On by default; not a switch for saving all chat history |
| Extraction frequency | High: each turn; balanced: every 3; economy: every 5; or off | Balanced by default; off stops new extraction, not recall |
| Deep extraction | Include reasoning, alternatives, and tradeoffs | Off by default; adds extraction usage |
| Extraction language | Language of new memories | Follows interface by default; does not translate existing items |
| Recall threshold | Strict, balanced, relaxed | Strict for fresh installs; balanced fallback for older configurations |
| Cross-project search | Retrieve relevant memories from other projects | Off by default; not blanket cross-project injection |
| Memory context length | Compact, balanced, detailed | Balanced by default; memory volume, not the model window |
| Synthesis frequency | Daily, weekly, off | Daily by default; off does not stop old-memory decay |
| Included extraction projects | Choose projects that create new memories | All included by default; exclusion does not delete existing items |
| Extraction model | Model and provider for background extraction | Defaults to a low-cost role; must be callable |
| Daily budget | Limit automatic extraction spending | Fresh baseline $10; older fallback $0.10; not total chat spending |
| Memories list | Search, filter, add, edit, pin, disable, restore, delete | At the bottom of Personalization; project options come from existing memories; adding without a project can be global |
Tool Assessment still has a settings row, but its related public tools are disabled; do not build a new workflow around it. Buddy is hidden. The separate “inject pinned memories” switch is also hidden; this differs from pinning an item in the list.
@Memory initiates work on Claude Code rule or memory files; it does not mean saving a database memory to this list. See memory and recaps. Configure Daily Briefing through its own page's gear.
Browser: backend, viewport, and profiles#
| Control | Purpose | Operation and limitation |
|---|---|---|
| AI browser control | Enable AI browser-control entry points in Settings → Browser | Off for fresh installs; existing enabled settings remain enabled; off does not clear site data |
| Native / External / Auto | Native by default; Auto prefers native, then external | Next browser call; external needs a working Chrome connection |
| Default viewport | Preset dimensions for new tabs | Defaults to panel size; existing tabs can override |
| Clear browsing data | Clear cookies, cache, and site data in the associated shared partition | Affects shared login state; does not guarantee clearing every profile |
| Profiles → New | Create separate cookie storage | Does not automatically switch the current or next conversation |
| Profiles → Import cookies | Import from detected browsers/profiles | Depends on platform and actual results; verify login afterward |
| Profiles → Delete | Delete a non-default profile and its login data | No delete action for the default profile |
| Control Chrome | Configure external Chrome control separately | Install the offered extension, enable, wait for readiness, and check tools in a new conversation |
Regular conversations currently have no visible Profile selector; default browser calls still use the default profile. Creating a profile does not establish account isolation between tasks. See the browser guide.
For an existing native browser tab, its toolbar menu also offers page zoom, viewport presets, and Cookies & browser settings. Cookie import there targets that tab's profile; refresh afterward and verify the account. See the browser example for a narrow-layout check.
Voice: recognition, polish, and history#
| Control | How to configure it | How to verify |
|---|---|---|
| Recognition models | Download a suitable language model, then select Use | Verify with a short recording |
| AI transcript polish | Enable for homophone and punctuation cleanup | On by default; sends text to the model provider |
| Polish model | Choose a working model | Defaults to a low-cost role |
| History and recordings folder | Inspect records and local audio | Check the latest record and open its audio file |
| Enable voice input | Off hides the microphone and disables its shortcut | Check the composer; on by default |
| Microphone selection | Authorize access, then choose system default or a detected device | Verify the selected device with a recording |
| Copy transcript | Copy a record's text | Paste into an empty draft to check |
| More actions → Download recording | Export the selected audio | Open the exported file |
| More actions → Delete recording | Delete the selected recording record | Confirm the target first, then inspect the list |
| History pagination | Browse more records | Check dates and content across pages |
Local recognition and AI polish are separate stages. There is no visible recording-retention-days setting. See voice dictation.
Correction preferences and vocabulary
Open Voice → Correction preferences → Manage. Write a short rule such as “Keep product names in English and preserve numbers,” then click Save preferences. Industry templates fill the editable instructions; review them before saving. Closing the dialog is not a substitute for this save action.
Under My words, add a correct spelling and optional common misspellings, then save the word. Learned words lists terminology extracted from clear edits made before sending: a later AI correction uses the same model to learn it, without an extra model request at send time. A single edit is not a promise that a word will be learned. Clearing learned words also removes pending learning examples, while keeping manual words and instructions.
To verify, reopen the preferences to check the saved rule, then dictate a short sentence and inspect its text. With AI correction off, saved correction preferences wait until it is enabled. In history, open a record to inspect Used text and any differing Original transcript or AI corrected text; identical versions do not require separate tabs.
Privacy: diagnostics and cleanup#
Diagnostic event logging is off by default. Enable it for a specific investigation, reproduce the issue, then disable it. Review session metadata before sharing logs.
Clear Local Data currently deletes the database and companion files, media, uploads, and images. It is not a way to clear CLI configuration, project files, all browser profiles, or voice recordings. See settings and data for locations and cleanup distinctions.
Local storage does not mean offline processing; data destinations still depend on the services you use.
Account and license: account and devices#
Inspect email, license status/type, start and expiry dates, and remaining days. Replacement is controlled by account eligibility. When offered, enter the new activation code, submit, then verify the updated status and dates.
The device list shows name, platform, version, and recent activity. It has no delete-device action. Signing out does not clear local conversations.
Archived sessions: restore or permanently delete#
Use search, project, and date filters to find a conversation. Preview it before restoring or deleting. After restoration, check the content in its project. Bulk actions are supported; Delete all applies to the filtered results.
Permanent deletion removes the selected conversations and messages and cannot be undone. Practice with a demo conversation rather than real history.
Keyboard shortcuts: edit, resolve conflicts, and reset#
- Search for a command, select edit, and press a combination.
- A valid, conflict-free combination saves directly; Escape cancels recording.
- Transfer resolves a conflict by removing that binding from the previous command.
- Clear a binding, restore one default, or confirm a reset of all bindings.
Commands have global, chat, file-panel, browser, and other scopes. Some entries, including double-Escape stop and Shift+Tab Plan switching, are fixed references. macOS screenshots and the double-Command gesture also require their respective system permissions.
Claude subscription usage: subscription limits#
This section shows the official Claude subscription account, limit windows, and behavior analysis, with refresh or retry. Relevant limits require a Pro/Max subscription login. API keys and third-party providers may not supply this data.
Temporarily unavailable does not mean zero quota. Read local token/cost statistics in Activity separately from these subscription limits.
If an option is missing#
- Check the applicable version at the top of this page and whether the relevant feature is enabled.
- CLI Agent Teams and the 1M context option remain experimental and depend on model, account, or platform support even when a control is visible.
- Platform-specific options appear only where supported; inspect the settings on the device where you will run the task.
- After changing a setting, verify it with the relevant message, notification, browser action, or recording.
Next steps#
Return to the settings map for common adjustments, use permissions to choose execution controls, or follow workflow tips.