Chat, manage agents, and review their work in one local desktop app.
Download · Docs · Contribute · CLI & Core · Website · X
OpenMinion Desktop is a local graphical workspace for the OpenMinion runtime. Chat with an agent, reopen conversations, manage profiles, review tool approvals, and inspect the local daemon without using a terminal. Execution, credentials, policies, and saved conversation history remain owned by OpenMinion.
Desktop is an early development alpha. The current application version is 0.0.10, versioned separately from OpenMinion. Fresh managed installations start with OpenMinion 0.0.29; compatible runtime updates are selected through the public runtime manifest. Unsigned development packages are available; signed stable releases and full Focus/CLI parity are still in progress.
Desktop UI preview with sample conversation data; no model or daemon is connected. Captured from current development source. Downloaded builds may differ.
- Install a development package or run from source.
- Follow First Launch to choose a provider and start chatting.
- Check At a Glance and Current Capabilities for supported behavior and remaining gaps.
- Use the documentation map for profiles, commands, data, troubleshooting, contribution, and release guidance.
- Official GitHub: https://github.com/openminion/desktop
- Official website: https://www.openminion.com
- Official X account: https://x.com/OpenMinion
OpenMinion has no official token, coin, NFT, airdrop, staking program, treasury product, or investment offering. Any claim otherwise is unauthorized and should be treated as a scam.
| Application | OpenMinion Desktop 0.0.10 · development alpha |
| Managed runtime | First install: openminion==0.0.29 from PyPI; updates: compatible public runtime manifests |
| Current runtime acceptance | macOS; Windows and Linux runtime certification remains open |
| Unsigned package formats | macOS DMG/ZIP, Windows ZIP, Linux DEB/ZIP |
| Source prerequisites | Node.js 24, npm 11, Python 3.11 |
| Best fit | Local text chat, saved conversations, profiles, and task controls |
| Remaining boundaries | Full Focus parity, media/artifact integration, remote daemons, signed stable distribution |
Download the unsigned 0.0.10 development build
from the official runtime repository. The release includes checksums and a
manifest identifying its exact source revision. The matching
Desktop source release
records the immutable source tag and package metadata. Use the
package selection and installation guide
to choose the correct architecture and verify its checksum. The published macOS
package is for Apple Silicon; no Intel Mac package is available in this release.
Development packages can lag this repository's dev branch; use source
development to test newer changes.
These packages are unsigned and macOS packages are not notarized. They do not establish stable-release or Windows/Linux runtime certification. Python 3.11 and network access are needed for the first managed-runtime installation. Desktop does not currently update its own application bundle. See Support for the supported environment and Releasing for package verification and release boundaries.
Use Node.js 24, npm 11, and Python 3.11. The current runnable development profile is macOS. The source repository is public.
git clone --branch dev https://github.com/openminion/desktop.git
cd desktop
npm ci
npm startTo explore sample UI interactions without a daemon or provider, use
npm run preview. The window is labeled UI preview; its sample results do
not prove that the corresponding runtime integrations are available.
For an existing source-installed runtime, use an isolated Desktop data directory:
OPENMINION_DESKTOP_HOME=/absolute/path/to/desktop-dev \
OPENMINION_EXECUTABLE=/absolute/path/to/venv/bin/openminion npm startThe executable needs a sibling openminiond entrypoint. This override is
unmanaged; Desktop does not upgrade it. See
Getting Started for lifecycle and Windows shell details.
On a fresh managed installation, Desktop installs openminion==0.0.29 from
PyPI under ~/.openminion/desktop, initializes a private local config, and starts
its daemon. First installation does not yet select a version from the runtime
manifest. Later launches reuse the installed runtime, including an activated
manifest-verified update. See runtime installation and updates.
In Welcome to OpenMinion:
- Choose a provider and enter its model and API key, or import an existing profile.
- Choose Set up and start. Test connection before continuing sends one provider request by default; clear it to save without testing.
- Write your first message and press Enter. Use Shift+Enter for a new line.
Try echo demo lets you explore text chat without a model credential. Setup uses OpenMinion's ordinary CLI provider catalog and setup flow. You can manage model and search-tool credentials later in Settings → Models & credentials.
Conversation names, unsent drafts, and display preferences persist in Desktop's SQLite database. Canonical transcripts and credentials remain in OpenMinion's own files. See Desktop Data before backing up or removing an installation.
| Area | Available today |
|---|---|
| Conversations | Create with a first message, search loaded names/IDs, rename, reopen, close, and export saved transcripts |
| Chat | Markdown replies, copy, reported duration/usage, live progress, cancellation, durable drafts, and Core-backed queued follow-ups during a turn |
| Recovery | Switch conversations during a turn; reconnect a known response without resending; reload saved history |
| Profiles | CLI-backed setup, profile import/add/edit, model and search-tool keys, and identity inspection/editing |
| Tools | Received output disclosure, saved display modes, request-bound allow-once/deny approvals, and supported exposure controls |
| Commands | Connected session, agent/tool/skill reports, task controls, and other commands listed in Desktop Commands |
| Runtime | Managed install/start/stop, status/log dialogs, version checks, and explicit preparation of eligible runtime updates |
Each operation depends on the installed runtime's public capability. The readiness matrix separates deterministic, native, managed-runtime, and published evidence. The Focus parity contract records remaining integration work; a visible command or preview control is not proof of full CLI parity.
Attachment sending, artifact browsing, and automatic watch are not connected. Screen/window selection provides an explicit local preview; macOS may request Screen Recording permission. Denying it leaves chat usable. Restart discovery of active turns, remote daemon attachment, and unrestricted native input are also outside the current supported behavior.
Runtime update controls apply to the managed OpenMinion installation, not the Desktop app. Only verified, explicitly compatible feed records can be prepared; activation occurs on a later startup. An empty or uncertified feed offers no update. See Runtime Updates.
| Component | Responsibility |
|---|---|
| OpenMinion | Agent execution, canonical sessions, tools, policy, credentials, and durable runtime state |
| Electron main | Desktop metadata, daemon lifecycle, authenticated communication, file grants, capture, and operating-system access |
| Preload | Narrow typed bridge exposing fixed application operations |
| Renderer | Chat, conversation navigation, settings, task controls, and local preview |
Desktop uses the ordinary public CLI and authenticated local API. It does not add another agent runtime or a Desktop-specific command to OpenMinion.
The renderer has no generic shell, filesystem, IPC, or network authority. Privileged operations stay in Electron main behind fixed typed methods. Stored credentials remain outside the renderer; newly entered keys are write-only inputs. Diagnostics may display CLI-reported paths, so review logs before sharing them. Screen observation begins only after explicit selection. Local storage does not make configured providers or tools offline. See Privacy and Connections for saved-key, backup, and network behavior. Read SECURITY.md for the full boundary and private reporting route.
Read CONTRIBUTING.md and CODE_QUALITY.md
before changing the application. Ordinary pull requests target dev; promoting
to main follows the separate release process.
| Command | Purpose |
|---|---|
npm run hooks:install |
Install the local repository hooks |
npm run ci-check |
Formatting, lint, types, public documentation, tests, and build |
npm run hooks:run |
Check hook parity and the current commit message |
npm run electron-check |
Provider-free native Electron smoke on macOS |
npm run package |
Build and inspect the native application directory |
npm run make |
Build and inspect this host's unsigned distribution artifacts |
Use focused tests during development and npm run ci-check before opening a
PR. Consult Testing And Validation for
integration prerequisites and the separate native, provider, and release gates.
src/main/ Electron lifecycle, daemon communication, files, and capture
src/preload/ Narrow typed renderer bridge
src/renderer/ Desktop workspace and presentation
src/shared/ Cross-process contracts
tests/ Unit, integration, lifecycle, and security proof
scripts/ Build and repository validation commands
docs/ Package documentation
The source tree owner map identifies existing owners for changes.
- Documentation: task-oriented guide to using and contributing
- Support: supported environments, troubleshooting, and bug reports
- API Compatibility: application/runtime contracts
- Changelog: versioned changes
- Releasing: unsigned builds, versioning, and stable release gates
- Public Source Readiness: public launch evidence and remaining acceptance
- Source code license: Apache-2.0
- Brand/trademark grant: none
The license grants rights to use, modify, and redistribute the code. It does not grant rights to present a fork, clone, token, website, or social account as the official OpenMinion project or imply affiliation or endorsement. See LICENSE and NOTICE.