Model or dataset
Open-Less/openless avatar
Open-Less/openless

openless states its platform list three different ways, and keeps a cloud key in the OS vault for the life of the install

Hold a key, speak, release: AI-polished text appears at your cursor in any app. Open-source voice input for macOS & Windows.

4,104 stars396 forksRustAGPL-3.0

At a glance

What is it?
A Rust voice input application for macOS, Windows and Linux that records speech, transcribes it, polishes it with an AI prompt, and inserts the result at the cursor of whatever window has focus, with a clipboard fallback. The README argues its case with three historical analogies and no measurement, and the metadata homepage points at a different account's repository.
Who is it for?
OpenLess is worth trying if you dictate long text into a focused editor and want it cleaned up on the way in, and the mechanics are unusually explicit for a project this young: you can read what permissions it wants, what it stores and what it shares. Three things to decide before you install it.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Rust, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Open-Less/openless4,104 ★ · +613
Star history
Repository2026-09-102026-11-15
Open-Less/openless3.5k4.1k

613 Stars in the last 66 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The homepage in the metadata names a different account

The repository's homepage field points at `github.com/appergb/openless`, which is not the account the repository lives in. The README's own links use `Open-Less/openless` throughout, for the releases page, the star count and the community invitation, so the file and the metadata disagree about where this project lives. There is a second, smaller disagreement in the same block. The licence badge points at the LICENSE file on the `main` branch, while the repository's default branch is `beta`. Neither of these stops anyone cloning the project, and both are the kind of detail that matters when you are following a link from a package index or writing a fork notice: the two facts a reader would use to confirm they have the right repository are the two that are wrong.

The platform list changes three times in one file

The header line says open source voice input for macOS, Windows and Linux. A few paragraphs down, the body describes the same product as a cross platform macOS and Windows voice input application, and drops Linux. The credits table then names a Linux maintainer, an Android author and Android maintainer, and a separate credit for macOS packaging and a developer account. So one file asserts three platforms in the header, two in the prose, and four in the credits. The Android entry is the odd one, since nothing else in the visible text mentions Android at all. For a project distributing binaries, this is not cosmetic: it decides which download you take and which missing feature turns out to be a platform you did not install.

A background process, a global hotkey, and whatever has focus

The mechanism is described in one paragraph and it is the whole design. Put your cursor in any text field, the file names ChatGPT, Claude, Cursor, Notion, an email draft and a chat box, press a single global hotkey, and speak. OpenLess records the audio, transcribes it, polishes the text in the mode you selected, and inserts the result at the cursor. If insertion is blocked, the text is copied to the clipboard instead, so nothing you said is lost. Two properties follow from that sentence. The application has to know which window has focus and write into it, which is what the accessibility grant is for. And the fallback path means dictated text can end up on the system clipboard when a target application refuses the insertion, which is the difference between a private note and one that lands in a paste buffer.

Microphone, accessibility and a cloud key, granted once

The section that argues the product matters also enumerates the permissions, which is unusually honest of it. On first run you grant the microphone, accessibility and cloud credentials exactly once. Tone sediments into a style pack that is switchable at a keystroke, proper nouns sediment into dictionary hotwords that the recognizer knows and the polish model is told about, where text lands sediments into the single insertion protocol, and model and credentials sediment into the OS vault, authorized once at launch and never renegotiated. So the cloud model credential is stored locally for the life of the install. Two opt-in features sit next to that: cursor context, macOS only, which lets the polish model read the text around your cursor, and a dictionary that asks once on a small card before remembering a correction. The file's word for that is that nothing is learned silently.

A style pack is a system prompt, and packs install with one click

The style pack feature is the part with the longest shadow. Instead of one fixed polish voice, you build style packs with custom system prompts, switch between them with a hotkey, install community packs in one click, and publish your own to the marketplace. The examples given are cold emails, commit messages, Xiaohongshu posts, formal reports and a team's tone. Read plainly, a pack is not a colour scheme, it is a set of instructions that will be sent to a model alongside whatever you dictated, and the distribution path is a public marketplace with a one click install. The file does not say what a pack is allowed to contain, whether a pack can be reviewed before it runs, or who is accountable for one that does something its author did not intend.

Three analogies, four named competitors, no numbers

The longest section of the README does not describe a feature. It argues that advanced systems turn today's communication into tomorrow's default rules, and supports that with three examples: the Internet won not because HTTP was faster, Git won not because the code was better, Stripe won not because payments were faster. Then the instruction to the reader: judge OpenLess not by how much faster it is, but by how much coordination it removes. The file names four commercial alternatives, Typeless, Wispr Flow, Lazy and Superwhisper, and compares itself to none of them on price, latency or accuracy. There is no timing, no accuracy figure and no table anywhere in what is visible, and the last line of the file breaks off mid-word, at streaming insertion described as flowing to the cursor character by character as it is poli.

Three betas in seven days, and two formats of the same version

The release list is three entries and they are close together: v2.0.0-Beta.2-tauri on 2026-09-24, v2.0.0-Beta.3-tauri on 2026-09-26 and v2.0.0-Beta.4-tauri on 2026-09-30. The default branch is `beta`, which matches. The tag and the release title disagree in shape, though: the tag carries a leading v, a capitalised Beta and a `-tauri` suffix, while the release is named OpenLess 2.0.0-Beta.4+build.20260930, with the build date appended after a plus sign. A script that parses one will not parse the other. The repository root carries the release process in `RELEASING.md`, usage notes in `USAGE.md`, two READMEs with a Chinese translation beside the English one, a `Casks/` directory for macOS packaging, and an `Examples/` directory holding a sample JSONL file of polish reference examples.

Editorial conclusion

OpenLess is worth trying if you dictate long text into a focused editor and want it cleaned up on the way in, and the mechanics are unusually explicit for a project this young: you can read what permissions it wants, what it stores and what it shares. Three things to decide before you install it. Understand that it runs in the background with the microphone and a global hotkey and writes into whichever window has focus, with the clipboard as the fallback, which means a hotkey misfire can put dictated text somewhere you did not intend. Read the community style packs as prompts rather than as themes, since a pack is a custom system prompt installed with one click and sent to a model. And pin a version deliberately, because the default branch is `beta`, the last three releases are three betas in seven days, and the tag names and the release names do not use the same format. The project is AGPL-3.0 licensed.

Frequently asked questions

What does openless do when I press the hotkey?

It records the audio, transcribes it, polishes the text in the mode you selected, and inserts the result at the cursor of whatever text field has focus. If insertion is blocked, the text is copied to the clipboard instead, so nothing that was said is lost.

Which platforms does openless run on?

The file says three different things. The header says macOS, Windows and Linux, the body describes it as a cross platform macOS and Windows application, and the credits table names a Linux maintainer and an Android author and maintainer alongside a macOS packaging and developer account credit.

What permissions does openless ask for?

On first run it asks for the microphone, accessibility and cloud credentials exactly once. Model and credentials go into the OS vault, authorized at launch and never renegotiated. Cursor context is opt-in and macOS only, and lets the polish model read the text around your cursor.

What is a style pack in openless?

A named, switchable set of custom system prompts that shapes the polish step. You can build your own, switch between packs with a hotkey, install community packs with one click, and publish your own to the marketplace. The examples given are cold emails, commit messages, Xiaohongshu posts and formal reports.

How is openless licensed?

AGPL-3.0, as recorded in the repository metadata, with a LICENSE file in the root. The licence badge in the README points at the LICENSE file on the `main` branch, while the repository's default branch is `beta`. The last three releases are all two point zero betas, dated 2026-09-24, 2026-09-26 and 2026-09-30.

Official sources

  1. License: AGPL-3.0
  2. Open-Less/openless on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/open-less-openless.svg)](https://hysenlabs.com/projects/open-less-openless)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/open-less-openless.svg)](https://hysenlabs.com/projects/open-less-openless)

Was this useful?