Open-source project
stevencohn/OneMore avatar
stevencohn/OneMore

OneMore: one add-in, five components, and published usage counts

A OneNote add-in with simple, yet powerful and useful features

3,451 stars255 forksC#MPL-2.0

At a glance

What is it?
A Windows add-in for a note-taking application that bundles a few hundred conveniences behind a keyboard palette, plus a command line runner, a calendar tool, a tray component, and a plugin architecture. The repository is more interesting than the marketing phrase suggests.
Who is it for?
OneMore fits a long-time user of that note application who wants formatting consistency across notebooks without rebuilding habits, and who is willing to work inside a Windows-only add-in model. Two things to check before installing.
Can I use it commercially?
Yes, with conditions. MPL-2.0 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly C#, 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

  • stevencohn/OneMore3,451 ★ · +38
Star history
Repository2026-09-272026-11-15
stevencohn/OneMore3.4k3.5k

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

Editorial analysis

A few hundred conveniences behind one install

The positioning is a joke with a serious installer: everything the note application should have shipped with, gathered as a few hundred small conveniences in a single add-in that installs in under a minute. The interface idea is that almost nothing should require the mouse. A command palette and a quick palette expose more than two hundred commands and styles without leaving the keyboard, and the two palettes are separate so the common case stays fast. Formatting consistency is handled by user-defined text styles and table themes that apply across every notebook rather than per page. There is an automatic table of contents for any page, section, or whole notebook that stays in sync as you type, Markdown pasting, syntax-highlighted code boxes, favourites with inline hashtags, image cropping and adjustment in place, and rendering of two diagram formats. Reusable snippets capture any block of content for later reuse.

The most-used commands are formatting, not structure

The readme publishes per-command usage counts gathered from real use across the community, and the ordering is the interesting part. Applying a text style runs over twenty-three thousand times a month. Pasting text as plain text runs a little over nine thousand. Inserting a table of contents, joining a paragraph, inserting a code box, and colourising code follow at between five and nine thousand. So the feature that dominates is applying a saved style, and the features that follow are text operations and content insertion. That profile says the add-in earns its place as a formatter and a paste tool rather than as a note-taking system in its own right, which is a different story from a tool that promises to restructure how you organise notes.

Usage counts are published next to a privacy statement

Two claims sit close together in the file and pull in opposite directions, so it is worth stating both without adding anything to them. The feature list says there is no subscription and no telemetry opt-in required, and the licence and privacy section says the project does not collect personal information and is committed to privacy, with a policy page linked for the detail. The usage figures at the top of the file can only come from somewhere, and the readme describes them as top commands from real usage across the community. Whether that reporting is anonymous, opt-in, or aggregated before it reaches the page is not stated in the file itself, which is why the policy page rather than the readme is the place to check. The stated licensing position is a Mozilla Public Licence 2.0, and the source is described as having been built in the open since 2018.

Five components where one add-in was expected

The repository is organised as several projects rather than one, and the components map onto different jobs. The primary add-in holds the source and the ribbon interface. A separate calendar application tracks page creation and modification dates, which is the kind of thing note-taking applications do badly and that is easier to bolt on than to build in. A command line runner automates the add-in's own commands. A tray application sits in the notification area. And a URI protocol handler exists purely for deep linking, so a link can open a note inside the application. Around those sit the parts nobody sees: an installation package with its own setup wizard, custom setup actions, bundle packaging utilities, a test project, and directories for plugins, reusable templates, and interface themes. The stated rationale is that the core add-in stays stable while the specialised pieces move independently.

The command line exists so automation does not bloat the add-in

The architecture section gives four reasons for the split, and one of them is a design argument rather than a convenience. A stable core add-in can be maintained without churning features into it. Automation can be provided through the runner without adding weight to the add-in people actually use. Plugin-based extensibility covers what the core deliberately omits. And concerns stay separated between the interface pieces, the core, and the tooling. The command line runner automates more than forty of the add-in's commands, which is the number to hold on to when deciding whether a workflow is scriptable: if a repeated action is not in those forty, it is probably a plugin's job. The protocol handler is the other quiet capability, since deep links into specific pages are what makes an external tool able to hand work to the add-in.

Visual Studio, PowerShell scripts, and one desktop edition

The build story is unambiguous about its platform. The code is C# against the .NET Framework, compiled through a Visual Studio solution with PowerShell scripts handling compilation and deployment, and the interface work spans the host application's ribbon plus desktop widget toolkits. The stated requirements are a specific Visual Studio community edition release, a specific .NET Framework patch level, and the desktop edition of the note application, which is not negotiable because everything is built on that application's object model. There is no command-line-only build and no headless mode, so the one-liner on the readme is about users installing a release rather than developers compiling one.

Three dates disagree, and the file tree is wider than the readme

A few small inconsistencies are worth recording because they say how the repository is maintained. The readme claims the project has been built in the open since 2018 while the copyright line reads a later year, which is normal for a project that outlived its original licence header. More usefully, the plugin directory appears in the file tree at the root but does not appear in the component list, even though plugin extensibility is one of the four stated architectural goals, so the readme's component list is a summary rather than a map. The root also holds a set of PowerShell scripts whose names describe the operational surface: setting the registry and the Office application state, registering the protocol handler through a registry file, stamping a version, fetching releases, updating the build SDK, stopping a running instance, and one script for finding unused resources, which is the kind of housekeeping a large resource-heavy project needs.

Editorial conclusion

OneMore fits a long-time user of that note application who wants formatting consistency across notebooks without rebuilding habits, and who is willing to work inside a Windows-only add-in model. Two things to check before installing. Confirm you have the desktop edition of the note application, since the whole thing is built on its object model and its ribbon, with no web or mobile path. And read the privacy statement alongside the usage statistics the project publishes, because the two describe the same product from opposite ends.

Frequently asked questions

what is onemore

An add-in for OneNote that bundles a few hundred conveniences into a single installation: over two hundred commands and styles reachable from a keyboard palette, user-defined text styles and table themes, an automatic table of contents, Markdown pasting, syntax-highlighted code boxes, favourites, hashtags, image editing, and reusable snippets.

how to add onemore to onenote

Download the latest release and follow the project's installation guide, which the readme says installs in under a minute. The desktop edition of OneNote is required, and the repository includes a setup wizard along with the registry and Office registration scripts used during installation.

is onemore safe

The project states there is no subscription and no telemetry opt-in required, says its privacy policy does not collect personal information, and has published its source on GitHub since 2018 under the Mozilla Public Licence 2.0. It also publishes per-command usage counts gathered from real use across the community, so the policy page is worth reading for detail.

Official sources

  1. Issues
  2. License: MPL-2.0
  3. README
  4. Releases
  5. stevencohn/OneMore on GitHub
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/stevencohn-onemore.svg)](https://hysenlabs.com/projects/stevencohn-onemore)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/stevencohn-onemore.svg)](https://hysenlabs.com/projects/stevencohn-onemore)

Was this useful?