Settings and data: find an option and verify a change
Find notification, appearance, model, network, memory, and storage settings, back up the database, check system permissions, and see where data is stored.
Settings & helpFind the setting for your task#
Click the account button at the bottom of the left navigation rail (its tooltip reads Account and settings) and choose Settings. On Windows you can also choose File → Settings at the top of the window. Settings are grouped into App settings, AI and connections, Coding, and Account and data. 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, send shortcut, background activity, or updates | App settings → General |
| Which events send system notifications and which sound each uses | App settings → Notifications |
| Theme, palette, fonts, sidebar, reading density, or motion | App settings → Appearance |
| Automatic naming, naming model, and reusable labels | App settings → Session organization |
| Edit or clear shortcuts, or bind global commands such as quick access | App settings → Keyboard shortcuts |
| Speech models, transcript-polish model, correction rules, or vocabulary | App settings → Voice |
| User rules, memory extraction, recall, budget, and the memory space | AI and connections → Personalization |
| Built-in tool groups available to the assistant | AI and connections → Tools |
| Model connections, provider and model configuration, default reasoning effort | AI and connections → AI services |
| Claude Code features, auto-compact timing, permission rules, or environment variables | AI and connections → Claude Code |
| Browser backend, browser identities, default viewport, and saved passwords | AI and connections → Browser |
| Servers, databases, APIs, and account credentials | AI and connections → Secrets and hosts |
| Saved proxy routes, the app proxy, and the browser default network | AI and connections → Network proxy |
| Git worktrees used by conversations | Coding → Worktrees |
| License and devices, Claude subscription limits, local usage and cost | Account and data → Account and license, Claude subscription usage, Activity |
| Status of screen recording, microphone, accessibility, and other system permissions | Account and data → System permissions |
| Diagnostic logging, data information, or Clear Local Data | Account and data → Privacy |
| Disk usage, old-conversation and preview cleanup, database backups | Account and data → Storage |
| Restore or permanently delete archived conversations | Account and data → Archived sessions |
See Conversation organization for titles and labels, Secrets and SSH for credentials and SSH hosts, and Worktrees for worktrees. Daily Briefing is retired. For a configurable replacement, install the official Daily review Skill and save its output in Space.
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.
When you upgrade from 1.3.1 or earlier, a few values follow new rules: an old proxy that was on but missing a host or port is treated as off; ⌥⌘K and ⌥⌘T are no longer bound by default; memory model calls count their actual cost against the daily budget, and early installs that never set a budget default to $1 per day. The settings reference lists the defaults field by field.
Useful adjustments#
Make the workspace easier to use
- Open Appearance → Theme and typography. Select Light, Dark, or System, then choose one of eight workspace palettes. Under fonts and sizes, adjust chat text size and message weight; for example, try 15px text with regular weight.
- In Appearance → Conversation display, try Relaxed reading density for long explanations, or Compact to fit more messages. Enable Message Navigator for long conversations.
- For quick editor access, enable External editor entry on the same tab, then choose the default tool in General → External applications.
Appearance choices save automatically and apply across conversations; the built-in terminal and code editor follow the workspace colors. If a save fails, use Retry; the interface restores the last saved appearance.
Organize the sidebar without changing your conversations
- Open Appearance → Sidebar and session list. Choose a layout preset, then adjust markers, channel/schedule icons, and activity status individually.
- Under Channel conversation titles, choose whether to display the sender and group/contact name. When both are enabled, the sender comes first.
- Under Navigation entries, toggle entries and drag to reorder them. Hidden entries remain in Explore; New session stays first.
Initial default width applies only before you resize the sidebar yourself. Dragging its edge sets a remembered width; double-click the edge to use the default again.
Start new tasks with appropriate permissions
- In General → New session defaults → Default Permission Mode, choose Default permissions, Auto mode, or Full access.
- Create a new conversation and check its permission selector. Existing conversations retain their own choices.
- Select Plan separately when you want an approach reviewed before execution. See permissions.
Get notified only when it matters
- Open Notifications → Notification types. For each event type (Needs your confirmation, Secret authorization, Task completed, Background tasks and subagents, Errors and failures), choose In-app and/or Desktop and pick a sound. Choose No sound to mute a type.
- When to notify under Task completed defaults to In background only: you are notified when you are not looking at that conversation, including when Onevium is in front but showing another conversation. Choose Always to be notified every turn.
- Under Desktop notifications → System permission, click Send test notification. On macOS the first notification raises the system prompt. If nothing appears, click Open system settings, allow Onevium, and turn off Do Not Disturb or Focus.
Choices save immediately. Run a short task, switch to another conversation while it finishes, and confirm the notification and sound for that type. The menu bar hub and the Dock menu open waiting, running, and recent conversations directly; see menu bar hub.
Route model requests through a proxy
- In AI services, verify the endpoint, credentials, and selected model. See custom providers for custom interfaces.
- Open Network proxy and click Add route… under Routes at the bottom. Enter a name, protocol (HTTP, HTTPS, or SOCKS5), address, port, and the username and password only if your proxy requires them. You can also paste
socks5://user:password@proxy.example.com:1080into Address to fill every field. Saving a route does not turn it on. - Under App proxy, set Mode to App Only, choose the saved route under Route, then click Test. With a single route it is chosen automatically; with no routes, the add-route dialog opens.
- A successful test shows the exit IP, latency, and test time. It describes the exit seen by the test service and does not validate your model account or endpoint. Send a short message in a new conversation to verify the model.
The app proxy covers model requests, image generation, and commands started in a new terminal. Programs already running, SSH, and external MCP servers are not moved onto it. Browser identities can use the same route; see the browser guide. Choose Global only when other applications should follow the proxy too: it writes the route into the system proxy and restores your previous setting when you switch back.
Back up the database and understand major upgrades#
Open Settings → Storage. The top shows how much space Onevium uses on this computer, by category (① in Figure 1). Database backups below can run on demand or on a schedule.
- On the Back up now row, click Create backup. When it finishes you see “Database backup completed.” and Last successful backup updates. You can keep using Onevium while it runs.
- For regular backups, turn on Automatic database backup (② in Figure 1), choose Every day or Every week and a weekday (③ in Figure 1), set Backup time and Automatic copies to keep (1–100, default 7), then click Save schedule.
- After saving, Next scheduled backup shows the next run. A missed backup runs once the next time Onevium starts.
- Expand Backup history to download a backup, or Backup location to see the folder.
Figure 1: ① usage by category, ② automatic database backup switch, ③ frequency, time, and copies to keep. Isolated demonstration of the real 1.3.2 storage settings; sizes, dates, and paths are fictional and no backup was run.
Database backups contain private conversations and settings. Original images, attachments, and project files are separate. Manual backups are always kept; the copies-to-keep limit applies only to automatic backups. Backups use disk space and are counted under Database backups.
On a major upgrade, the first launch shows real progress on the startup page: backing up your data, verifying the backup, then upgrading your data. The pre-upgrade snapshot is kept in upgrade-backups inside the data directory. After upgrading to 1.3.3, 1.3.2 cannot read the new data directly; do not open the upgraded database with an older version, and do not delete the upgrade snapshot.
System permissions and the keychain#
Open Settings → System permissions to see the status of Microphone, Camera, Screen and system audio, Accessibility, Automation, Files and folders, and Notifications. Opening this page does not request access or start capturing.
Figure 2: each permission shows its purpose and system status; for example, Screen and system audio is Not allowed by the system. Isolated macOS demonstration of the real 1.3.2 system permissions component; statuses are fictional and no real permission was read or changed.
- When a permission is Not requested yet, click Request permission. Otherwise use Open system settings to reach the system pane, or a button such as Go to Voice to reach the related feature.
- Not allowed by the system appears in red. After changing system settings, return to Onevium, click Check permissions again, and try the feature. An allowed status is the system check, not a successful capture test.
- Items showing Check in system settings cannot be read reliably here. Check them in system settings and try the feature.
If a permission is on but still not working on macOS: after an update or a signing identity change, macOS may keep an old permission entry. Fully quit Onevium, reopen it from Applications, and check again. If access is still denied, turn the permission off and on in System Settings; where supported, remove the old entry and add the current app. Starting with 1.3.2 the app uses a fixed signature, so after upgrading to 1.3.2 grant screen recording, microphone, and input monitoring once more.
Keychain password or Touch ID prompts are separate from these permissions: the first launch of each new version asks once for your login password to access the keychain. Choose Always Allow. Screen recording and microphone permissions do not unlock keychain credentials.
Confirm when a change takes effect#
| Setting style | When it takes effect | How to check |
|---|---|---|
| Most switches, selectors, and notification types | 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 |
| Backup schedule | Click Save schedule | Next scheduled backup appears |
| Proxy routes | Click Save in the add/edit route dialog | The route appears in the list; a test shows its exit and time |
| User rules and extra direct addresses | When you leave 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 default reasoning effort | 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, uploads, and images | ~/.onevium/ on macOS/Linux; %APPDATA%/Onevium on Windows. A custom data directory can differ; Storage → Storage locations shows the real folder |
| Database backups | db-backups in the data directory; Storage → Backup location shows the real folder |
| Pre-upgrade snapshots | upgrade-backups in the data directory |
| Worktrees created by Onevium | worktrees in the data directory by default; managed under Coding → Worktrees |
| 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 identity; tabs using it 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 the cleanup actions#
- Storage → Clean up old conversations: review conversations and their sub-conversations before moving them to the trash. Clear rebuildable previews removes cached image previews only; original images, attachments, and logs are kept. The Storage page never deletes an active database or compacts it automatically.
- Archived sessions: preview, restore, or permanently delete selected conversations.
- Browser → Clear browsing data: deletes cookies, cache, and site data shared by all browser tabs; several tabs may lose their login.
- Privacy → Clear Local Data: deletes the Onevium database and the media, uploads, and images directories. Space resources are preserved; clear them through their own resource actions when intended. It does not clear project files, CLI settings, browser identities, or voice recordings, and it does not delete backups in
db-backupsorupgrade-backups.
Create a database backup in Storage 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.
- Every request fails while the proxy is on: if the Route row says the proxy is on but its route is unavailable, choose a route again or set Mode back to Off. An incomplete proxy from an older version is treated as off; add a complete route first.
- The test succeeds but the model still fails: the test only checks the exit seen by the test service. Recheck the endpoint, credentials, and model in AI services.
- No notification: click Send test notification in Notifications, check system notification permission and Do Not Disturb. Task completed notifies only when you are not viewing that conversation by default.
- Screen recording or microphone stops working after an upgrade: click Check permissions again in System permissions, then fully quit and reopen or grant access again as described above.
- The last backup did not finish: check free disk space and folder access, then click Create backup again.
- Old facts appear after extraction is disabled: extraction controls new memories; recall is separate. Check Personalization → Memory space.
Include Space in a full backup
Space uses a separate space directory containing its database, resource files, attachments and versions. Create backup and the automatic main-database schedule do not constitute a complete Space backup. For a machine move or beta rollback, fully quit Onevium and copy the entire active data directory to a private backup location. Keep original project files separately too. Open a copied resource and its history after restoring; a backup filename alone does not prove all files were included.
The 1.3.3 main-database upgrade is one-way for older applications. Preserve the pre-upgrade snapshot and current data before attempting a rollback; see installation and updates.
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.