limetext/lime

Analysis updated 2026-06-24

★ 15,276Audience · developerComplexity · 4/5LicenseSetup · hard

Mindmap

mindmap
  root((lime))
    Inputs
      Source files
      Sublime Text plugins
    Outputs
      Edited text
      Plugin events
    Use Cases
      Edit code with a Sublime-like UI
      Run Sublime plugins on open source stack
      Contribute to a text editor project
    Tech Stack
      Go
      QML
      termbox
      HTML

mindmap root((lime)) Inputs Source files Sublime Text plugins Outputs Edited text Plugin events Use Cases Edit code with a Sublime-like UI Run Sublime plugins on open source stack Contribute to a text editor project Tech Stack Go QML termbox HTML

Click or tap to explore — scroll the page freely

What do people build with it?

USE CASE 1

Contribute to an open source Sublime Text alternative

USE CASE 2

Experiment with running Sublime Text plugins on an open backend

USE CASE 3

Study how a multi-frontend editor architecture is split between core and UI

USE CASE 4

Build a custom frontend on top of the lime backend

What is it built with?

GoQMLtermboxHTML

How does it compare?

	limetext/lime	checkly/headless-recorder	tencent/weui-wxss
Stars	15,276	15,276	15,279
Language	—	JavaScript	Less
Setup difficulty	hard	moderate	easy
Complexity	4/5	2/5	2/5
Audience	developer	developer	developer

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Frontends are incomplete, expect build issues and missing features compared to Sublime.

2-clause BSD license, free to use and modify with attribution.

In plain English

Lime is an open source text editor built as an API-compatible alternative to Sublime Text. The project was started by someone who loved Sublime Text but grew concerned about its closed-source nature and slow development pace, wanting a replacement that could run the same plugins and extensions without locking users into a proprietary product. The project is organized as a meta repository, with separate components for the backend logic and three different frontends: one built with QML for a native desktop feel, one for terminal use via termbox, and one HTML-based option. The API compatibility goal means that existing Sublime Text plugins should work with Lime without requiring developers to rewrite or duplicate their work for a different interface. At the time of this writing, the frontends are not ready to replace a daily-use editor, though the backend is described as progressing. The project welcomes contributions, anyone can claim an open issue and submit a pull request. If you want to help build Lime, the wiki contains pages on goals, building instructions, and contributing guidelines. The project is released under the 2-clause BSD license.

Copy-paste prompts

Prompt 1

Walk me through the lime repo layout and explain how the backend talks to the QML and termbox frontends

Prompt 2

Show me how Sublime Text plugin API compatibility is implemented in the lime backend

Prompt 3

Help me build the lime QML frontend on Linux and list the dependencies I need

Prompt 4

Pick a good first issue in lime for someone who knows Go but not editor internals

Frequently asked questions

What is lime?

Open source attempt to clone Sublime Text with API compatibility so existing plugins keep working. Backend is progressing, frontends (QML, termbox, HTML) are not daily-driver ready.

What license does lime use?

2-clause BSD license, free to use and modify with attribution.

How hard is lime to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is lime for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub limetext on gitmyhub

Verify against the repo before relying on details.