Settings and data: find an option and verify a change

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, window pinning, new-session permissions, notifications, or background activity	General
Light/dark mode, workspace palette, fonts, text size, or weight	Appearance → Theme and typography
Conversation markers, source/status positions, sidebar text size, width, or channel-title prefixes	Appearance → Sidebar and session list
Reading density, process display, message navigation, or editor/commit toolbar entries	Appearance → Conversation display
Decorative effects or hardware acceleration	Appearance → Motion and performance
Default external editor or terminal	General → External applications
Each model's default reasoning effort	Providers → the provider's model configuration → Default reasoning effort
Model connections, providers, and model configuration	Providers
Claude CLI features, permission rules, or environment variables	Claude Code
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, transcript-polish model, correction rules, or vocabulary	Voice; rules and vocabulary are under Correction preferences → Manage
Diagnostics, data information, or local cleanup	Privacy
License/devices, archived conversations, or shortcuts	Account and license, Archived sessions, Keyboard shortcuts
Claude subscription limits and account usage	Claude subscription usage

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.

For microphone selection, history actions, and other detailed controls, open the settings reference and check its applicable version.

Useful adjustments#

Make the workspace easier to use

1. Open Appearance → Theme and typography. Select Light, Dark, or System, then choose one of eight workspace palettes. Each palette has light and dark colors; switching palettes also selects its matching link and focus color.
2. Adjust chat text size and message weight in Fonts and sizes. For example, try 15px text with regular weight, then check the live conversation preview. Interface, message, and code fonts have separate controls.
3. In Appearance → Conversation display, try Relaxed reading density for long explanations, or Compact to fit more messages. Choose full process details when debugging, or hide details when focusing on results. Process visibility affects presentation and preserves individual conversation choices.
4. Enable Message Navigator in the same tab for long conversations. For quick editor access, enable External editor entry here, then choose the default tool in General → External applications.
5. Return to General for language and desktop notifications. Allow Onevium in system notification settings and verify delivery with a short task.

Appearance choices save automatically and apply across conversations. The built-in terminal and code editor also follow the workspace colors. Reopen Settings and check an existing conversation to confirm the saved result. If a save fails, use Retry; the interface restores the last saved appearance.

The screenshot below shows the earlier settings layout. Use the section paths above to locate appearance controls in the current layout.

Enlarge imageOriginal General settings content with the example host cropped out. Selected values are example configuration; upgraded installations may differ.

Organize the sidebar without changing your conversations

1. Open Appearance → Sidebar and session list. Choose a layout preset, then adjust markers, channel/schedule icons, and activity status individually if needed.
2. Try Status on the right with the default sidebar text size. Check the live examples and a real conversation row; message and code sizes are independent.
3. Under Channel conversation titles, choose whether to display the sender and group/contact name. When both are enabled, the sender comes first.
4. To reorder the upper-left navigation, right-click that navigation area and choose Customize, drag the entries, toggle their visibility, then click Done. The same controls are available under Navigation entries in the sidebar settings tab. Hidden entries remain in Explore; New session stays first.

Initial default width applies before you resize the sidebar yourself. Dragging its edge sets a remembered width; changing the default does not overwrite that choice. Double-click the edge to use the configured default again. Reopen the settings and verify the saved layout instead of resetting other preferences.

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.

Diagnose a model or network connection

1. In Providers, verify the endpoint, credentials, and selected model. See custom providers 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
Workspace colors, fonts, text size, weight, and density	Automatic save; shared across conversations	Check the preview and an existing conversation; confirm no save error remains
Voice correction instructions	Click Save preferences; adding or editing a word uses its own Add word / Save word button	Reopen Correction preferences and check both the rules and vocabulary
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 in General and reasoning effort in provider model configuration	New conversations; individual sessions can override	Create a new conversation with the relevant provider and model
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; screenshots from a different version may differ.
• Theme or process controls are missing from General: open Appearance. Reasoning defaults are in the relevant provider's model configuration and appear only for models with more than one supported effort level.
• 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 and practical examples in workflow tips. Adjust the few settings that matter to your current work, then refine them from observed results.