Onevium
GitHubDownload
Introduction

Getting started

Install Onevium on macOS, Windows, or Linux, connect your Anthropic API key, and learn the core interface surfaces.

Updated 2026-03-25

Install the desktop client

Onevium is available as a native desktop app for all three major platforms. Download the installer from the GitHub releases page.

  • macOS: Open the .dmg file and drag Onevium to Applications. Both Apple Silicon (arm64) and Intel (x64) builds are available.
  • Windows: Run the .exe installer (NSIS) or extract the .zip for a portable installation. Supports x64 and arm64.
  • Linux: Choose between .AppImage (portable), .deb (Debian/Ubuntu), or .rpm (Fedora/RHEL). Supports x64 and arm64.

Sign in and connect your API key

On first launch, Onevium asks for your email address. A verification code is sent to your inbox — enter it to complete authentication. If you have a license key, activate it in Settings.

Onevium connects directly to the Anthropic API using your own key. Go to Settings > API Providers and add your Anthropic API key. All requests go straight to the API — no proxy or intermediary.

Choose a project and start a session

Every chat session is scoped to a working directory. Select a project folder to give Claude full context of your codebase — file reads, edits, terminal commands, and skill/agent discovery all operate within this directory.

The three interface areas

The Onevium interface is divided into three main zones:

  • Sidebar (left): Project switching, session history, Automations, Channels, and Settings navigation.
  • Conversation panel (center): Chat with Claude, see tool execution in real-time, approve or deny actions, switch between models (Opus, Sonnet, Haiku).
  • Context panel (right): Browse the project file tree, pin files to the context basket. Pinned files are automatically included as @mentions when you send a message.

Permission modes

Control how much autonomy Claude has during a session. You can change the mode at any time from the toolbar.

  • Default: Claude asks for approval before edits, shell commands, and other sensitive actions. File reads are auto-approved.
  • Full Access: All tool calls are auto-approved. Best for trusted workflows where you want uninterrupted execution.
  • Plan Mode: Claude proposes changes as a structured plan first. You review and approve the plan before any code is written.

Where data is stored

All Onevium data lives locally in ~/.onevium/. Nothing is written to your project directories unless Claude explicitly creates or edits files during a session.

  • onevium.db — SQLite database (WAL mode) for sessions, messages, schedules, channel config, and audit logs.
  • media/ — Generated images and media files.
  • uploads/{sessionId}/ — Files uploaded during conversations, isolated per session.