> Source: Onevium official documentation > Article: Settings and data: find an option and verify a change > Original URL: https://onevium.com/docs/settings-and-data > Language: English > Updated: 2026-09-09 > Applies to: 1.1.22 > Feature status: Released --- # Settings and data: find an option and verify a change Find appearance, model, permission, memory, browser, and network settings, with their save behavior and actual data scope. ## Find the setting for your task Open Settings from the sidebar. Choose a section by the problem you want to solve; you do not need to configure every option. | What you want to change | Where to go | | ----------------------------------------------------------------------- | ---------------------------------------------- | | Language, theme, process display, message navigation, or window pinning | General | | New-session permissions and each model's default reasoning effort | General | | Editor/commit toolbar entries, notifications, or background activity | General | | Model connections, providers, and model configuration | Providers | | Claude CLI features, permission rules, or environment variables | Claude CLI | | Proxy endpoint, authentication, or extra direct addresses | Network proxy | | Local activity, estimated cost, tokens, and cache | Activity | | Built-in tool groups available to the assistant | Tools | | User rules, memory extraction, recall, and budget | Personalization → Memory settings | | Inspect, correct, or disable saved memories | Memories at the bottom of Personalization | | Browser backend, default viewport, or cookie profiles | Browser | | Speech models and transcript-polish model | Voice | | Diagnostics, data information, or local cleanup | Privacy | | License/devices, archived conversations, or shortcuts | License, Archived sessions, Keyboard shortcuts | | Claude subscription limits and account usage | Usage & billing | Daily Briefing generation time, included projects, and output language are configured through the **gear on the Daily Briefing page**. ## Check the current value first Upgrades preserve existing choices. Fresh-install defaults, fallback values for older configurations, and your current selections may differ. Do not reset settings merely to match a screenshot. This guide focuses on settings present around version 1.1.22. Development-version differences, including microphone selection and enhanced history actions, are identified in the [settings reference](https://onevium.com/docs/settings/reference). ## Three useful adjustments ### Make the workspace easier to use 1. Select your theme and language in General. 2. Choose full process details when debugging, or hide details when focusing on results. This changes presentation only. 3. Enable Message Navigator for long conversations. For quick editor access, enable External editor entry and choose its default tool. 4. Enable desktop notifications if you need completion alerts, then allow Onevium in system notification settings. Verify delivery with a short task. ![General appearance, process view, and default permissions](https://onevium.com/assets/docs/settings-general-en.png "Original General settings content with the example host cropped out. Selected values are example configuration; upgraded installations may differ.") ### Start new tasks with appropriate permissions 1. Choose the starting profile in General → Default Permission Mode. 2. Use Auto for routine work, Default when you want to review tool requests as they arise, or Full Access for explicitly authorized work in a trusted environment. 3. **Create a new conversation** and check its permission selector. Existing conversations retain their own choices. 4. Select Plan separately when you want an approach reviewed before execution. See [permissions](https://onevium.com/docs/permissions). ### Diagnose a model or network connection 1. In [Providers](https://onevium.com/docs/providers), verify the endpoint, credentials, and selected model. See [custom providers](https://onevium.com/docs/providers/custom) for custom interfaces. 2. If a proxy is needed, start with App Only. Enter the protocol, host, port, and optional authentication supplied by the proxy operator, then test. 3. The proxy test checks a tunnel to an IP echo service and may show that request's exit IP. It **does not validate your model account, model endpoint, or browser exit**. 4. Send a short message in a new conversation to verify the model itself. Consider Global only when other applications should also use the proxy. ## Confirm when a change takes effect | Setting style | When it takes effect | How to check | | ---------------------------------------- | -------------------------------------------------------- | ----------------------------------------------------- | | Most switches and selectors | Saved when selected | Reopen the section, then exercise the feature | | User rules and proxy text | After a short pause or leaving the field | Navigate away and back to confirm the text | | CLI permission rules and advanced JSON | Explicit Save; advanced changes may ask for confirmation | Check valid JSON, save, and test a new conversation | | Default permissions and reasoning effort | New conversations; individual sessions can override | Create a new conversation | | Default browser viewport | Newly opened tabs | Open a new page and inspect its size | | Disable hardware acceleration | After restarting the app | Save your work, restart, and inspect display behavior | After enabling tools or changing a connection, verify an actual call. A saved configuration is not a successful business operation. ## Where data is stored | Content | Typical location and scope | | ------------------------------------ | ------------------------------------------------------------------------------------------------ | | Onevium database, media, and uploads | `~/.onevium/` on macOS/Linux; `%APPDATA%/Onevium` on Windows. A custom data directory can differ | | User CLI settings | `~/.claude/settings.json`; changes may also affect Claude CLI using that configuration | | User Skills and Agents | `~/.claude/skills/` and `~/.claude/agents/` | | Project extensions and rules | The project's `.claude/`, `CLAUDE.md`, and related files | | Project MCP | `.mcp.json` in the project root, not `.claude/settings.json` | | Voice recordings | Use Voice → Open recordings folder to locate them | | Browser cookies and site data | The relevant browser profile; tabs using it can share login state | Model requests go to your selected provider. Remote websites and MCP can also use the network. Local storage does not mean all processing is offline. ## Distinguish three cleanup actions - **Archived sessions:** preview, restore, or permanently delete selected conversations. - **Clear browsing data:** affects cookies, cache, and site data in the associated browser partition; several tabs may lose their login. - **Privacy → Clear Local Data:** currently deletes the Onevium database and media, uploads, and images directories. It does not mean every Onevium-related file is removed. Do not assume it clears project files, CLI settings, browser profiles, or voice recordings. Keep a copy of anything you need before cleanup. Do not clear data to troubleshoot an ordinary connection failure. ## Common problems - An old conversation ignores a change: check whether it is a new-session default or has a session override. - An option is missing: check the platform, installed version, and required feature state; beta screenshots may differ. - No notification: check system permissions, Do Not Disturb, and whether you use an installed build. - Old facts appear after extraction is disabled: extraction controls new memories; recall is separate. ## Next steps Find individual fields in the [settings reference](https://onevium.com/docs/settings/reference) and practical examples in [workflow tips](https://onevium.com/docs/workflows/tips). Adjust the few settings that matter to your current work, then refine them from observed results.