hackjutsu/Lepton: A GitHub Gist Snippet Manager for the Desktop

What Lepton solves for people who already keep snippets in Gist

GitHub Gist is a fine storage layer and a poor browsing interface. It gives you unlimited public and secret snippets, versioning and a URL, but it offers no tag system, no language grouping and no fast local search across everything you have written. Lepton exists to put a desktop client on top of that storage. The README describes it as "a lean code snippet manager powered by GitHub Gist", and the feature list is essentially the missing Gist UI: unlimited tags, language groups, Markdown and Jupyter Notebook rendering, a dashboard, and a search bar bound to Shift + Space.

The audience is narrow and specific. If your snippets already live in Gist, or you want them to, Lepton is a front end for that account. If you have never used Gist, adopting Lepton means adopting Gist as your storage model first. That is a real decision, not a detail: the app's data lives in your GitHub account, and the README does not describe a local database that survives independently of it.

How the Gist sync model actually works

Lepton is an Electron application. The README lists the stack: Electron for the shell, Webpack and Babel for bundling, React 19 with Redux and Redux Thunk for UI and state, CodeMirror and Highlight.js for editing and rendering. The repository layout confirms the split, with main.js and preload.js at the top level alongside an app/ directory, which is the standard Electron arrangement of a main process plus a renderer bundle.

Sync is manual and explicit. Cmd/Ctrl + R is bound to "Sync snippets with GitHub Gist", and Cmd/Ctrl + S submits changes from the editor. That two-step model matters: editing a snippet in Lepton does not push it to GitHub until you submit and sync. The README does not document automatic background sync, conflict resolution, or what happens when the same Gist is edited in the browser and in the app between syncs. Treat the sync button as the boundary of consistency.

Authentication has two paths. The app supports a GitHub token, and it also supports OAuth through a registered GitHub application. For GitHub Enterprise deployments the README points to a wiki FAQ entry on enabling it, which suggests the API base URL is configurable rather than hardcoded. The configuration surface is a single file, .leptonrc, in your home directory, whose exact path the About page shows via Cmd/Ctrl + ,. That file is where theme, editor, logger, proxy, shortcuts, zoom, enterprise settings, notifications and interface language are set.

Installing Lepton and syncing your first Gist

The README gives three installation routes. Released packages for macOS, Windows and Linux are on the releases page. macOS users can install through Homebrew:

brew install --cask lepton

Linux users can install through the Snap Store:

snap install lepton

After launching, the first real task is authentication. If you build from source rather than installing a release, you must register a GitHub application and create configs/account.js with your client id and secret:

module.exports = {
  client_id: <your_client_id>,
  client_secret: <your_client_secret>
}

The README notes that configs/account.js is ignored by Git and that a missing file falls back to configs/accountDummy.js, which supports rendering tests but not real GitHub login. Release builds generate that file from GitHub Actions secrets before packaging, so this step only concerns source builds.

To build and run from source, the README recommends Node.js 24 LTS and npm 11.x, and the repository ships an .nvmrc:

nvm install
nvm use
npm ci
npm run build && npm start

Once signed in, press Cmd/Ctrl + R to pull your Gists. You should see your existing snippets appear with language groups and tags. Create one with Cmd/Ctrl + N, save with Cmd/Ctrl + S, then sync again with Cmd/Ctrl + R to push it to GitHub, and confirm it appears in your Gist account in the browser. That round trip is the single most useful thing to verify before trusting the app with a working set of snippets.

Customization through .leptonrc, and where the documentation thins out

The .leptonrc file is the whole configuration story, and it is broader than a theme picker. It covers snippet behaviour, the editor, logging, proxy settings, keyboard shortcuts, zoom, enterprise endpoints, notifications and interface language. Themes ship as a fixed list: light, dark, one-dark, atom-one-dark, github-light, github-dark, catppuccin-latte, catppuccin-mocha, solarized-light, solarized-dark, dracula, material-theme and ayu. Interface locales are en, es, fr, ja, ko, tr, zh-Hans and zh-Hant, set through the i18n.locale key.

The README does not print the schema of .leptonrc. It says to create the file if it does not exist, shows the key names as a bulleted list, and defers to a separate configuration document in the wiki. That is a gap worth naming: a configuration file whose keys are documented only in a linked wiki page is easy to get wrong, and a malformed file has no documented failure behaviour. The proxy support, which the feature list mentions and the FAQ links to, is likewise described only by reference. If your environment requires a proxy to reach GitHub, read the wiki entry before you assume the setting works as you expect.

Where Lepton is the wrong tool

Lepton is a client for Gist, so it inherits Gist's constraints. There is no documented offline mode. If GitHub is unreachable and you have not synced, the README does not describe a local store that serves your snippets anyway. There is no documented conflict resolution either, which is the predictable consequence of editing the same Gist in two places. A team that edits shared snippets in the browser and in the app simultaneously has no stated merge behaviour to rely on.

The app is also desktop-only. The topics list desktop-client and electron, and the platform line is macOS, Windows and Linux. There is no mobile client and no web client in the README. And there is no hosted team tier: Lepton is a free, MIT-licensed local application, and the README explicitly says the project does not accept donations, offering a coffee link for the maintainer instead. If you need shared team snippet permissions, an audit trail, or an API other tools can call, Gist plus Lepton gives you none of that. Finally, the release history shows the current line is beta: v2.0.1-beta.1 and v2.0.1-beta.2 were published in August and September 2026, after the v2.0.0 release in July 2026. The beta tag is not a defect, but it is a signal about where the stable channel sits.

Lepton compared with a local-first snippet manager

The clearest alternative in kind is a local-first snippet manager that stores snippets in a file or local database on your own machine and treats cloud sync as an optional add-on. The difference is architectural, not cosmetic. A local-first tool works with no network, and its sync layer can be swapped or disabled. Lepton inverts that: GitHub Gist is the source of truth, and the desktop app is a view over it. You get versioning, shareable URLs and zero server maintenance for free, because GitHub already provides them. You give up independence from GitHub's availability and from its account model.

That trade is reasonable for an individual developer whose snippets are personal, whose network is usually up, and who values having a URL for every snippet. It is a poor trade for anyone who needs snippets available on a plane, or who cannot put internal code fragments into a third-party account at all. Note also that Gist visibility is a per-snippet choice: the feature list distinguishes public and secret snippets. Secret is not the same as private to an organization, and the README does not make a stronger confidentiality claim than that.

Licence, build dependencies and what maintenance costs you

Lepton is MIT licensed, and the repository carries a license.json produced by a license-checker step in the build. The package.json build script runs that check before webpack, and the dist, pack and release scripts all run a package:prepare step that regenerates it. Practically, that means a source build pulls in the Electron, React, Redux, CodeMirror and Highlight.js dependency trees, and the project records their licences for you. MIT on Lepton itself is permissive, but it says nothing about the transitive dependencies, which is exactly why that generated file exists. Read license.json rather than assuming the whole bundle is MIT.

The upgrade surface is the Node and npm toolchain plus Electron. The README pins the development runtime at Node.js 24 LTS and npm 11.x, with Node.js 24.18.0 and npm 11.16.x listed as recommended, and it notes that Apple Silicon development should use the native arm64 Node.js runtime. There is a check-outdated script for inspecting stale dependencies, and a preversion script that runs lint, the full test suite (Vitest unit tests plus a build test) and that outdated check before a version bump. That is a heavier gate than many small Electron projects carry, and it is the honest cost of contributing: your change has to pass lint, unit tests and a webpack build before it ships. The last push to the repository was on 2026-09-15.

Editorial conclusion

Adopt Lepton if your snippets already live in GitHub Gist and you want a desktop client with tags, search and Markdown rendering rather than the GitHub web UI. Skip it if you need offline-first storage, a self-hosted sync server, or a native mobile client, because the README documents none of those. Before committing, verify two things: that your GitHub account can hold the number of Gists you plan to create, and that a test Gist survives a Cmd/Ctrl + R sync round trip, since the README does not document rollback behaviour for a failed or conflicting sync.

Frequently asked questions

Official sources

1. hackjutsu/Lepton on GitHub
2. License: MIT
3. Project website
4. README
5. Releases