Scribe icon
Scribe icon

Scribe

Vim-flavoured modal editor with the parts a writer actually needs and a few features vim never had. Single static binary, sub-10 ms startup, soft-wrap by default, Claude Code in the editor, syntax highlighting, hunspell spellcheck, Goyo-style reading mode, persistent registers...

Cost / License

Platforms

  • Mac
  • Windows
  • Linux
  • BSD
  • Rust
1like
0articles
Save

Features

Properties

  1.  Privacy focused

Features

  1.  Works Offline
  2.  Syntax Highlighting
  3.  Ad-free
  4.  Spell Checking
  5.  No registration required
  6.  Full-Text Search
  7.  No Tracking
  8.  Modal editor
  9.  Support for Keyboard Shortcuts
  10. Claude icon  Claude Integration
  11.  Reading mode
  12.  Integrated Search
  13.  Text Wrapping
  14.  Vim Key Mapping
  15.  Keyboard Navigation

Scribe News & Activities

Highlights All activities

Recent activities

Scribe information

AlternativeTo Categories

Office & Productivity, OS & Utilities, Development, AI Tools & Services

GitHub repository

  •  68 Stars
  •  1 Forks
  •  0 Open Issues
  •   Updated  
View on GitHub
Scribe was added to AlternativeTo by Paul on and this page was last updated .

No comments or reviews, maybe you want to be first?

Featured in Lists

Open-Source Slopware

A list of open-source software containing slop (LLM generated) code or endorses the usage of LLMs in other ways. This list contains software that obviously accepts irresponsible coding practices or promotes LLM usage. I found these applications while searching for alternatives to previously used software that turned out to contain code generated by slop-machines. Each of added applications have at least one link that points to the verifiable proof. This list by no means is meant to cover all the software that contains code by not-so-intelligent tools and people using them but to serve as a reminder to myself about what I have already checked. Why having LLM generated code (and using generative tools in general) is bad? Ethical reasons — such as illegally retrieved training material, underpaid workers that prepare the training data. Impact on environment — increased fossil fuel usage to supply the needed electricity power, water usage in water scarce regions. This somewhat overlaps with the above. Social impact – noise pollution in neighbourhoods near AI data centres, air pollution from diesel- or gas-powered turbines (also overlaps with the above), resource consumption by data centres drastically increases utility prices. Impact on brain and thinking, reasoning — by offloading thinking and decision making to machines people are shooting in their foot (more like in their head) as this leads to brain rot. Less intelligent people are easier to control. Even legal issues (especially in open-source software as it cannot be guaranteed that the “generated” code is not really just re-used, thus unknowingly violating the source license). Inevitable enshittification — every software product from big technology eventually gets enshittified to maximize revenue. For users this could mean hidden or plain ads, biased opinions/information, privacy violations, increased prices for LLM based tools. Burden on open-source software maintenance — LLM tools provide easier access to code contributions which often shifts the responsibility of checking code quality from developers to maintainers and reviewers. Digging through walls of merge request text and code generated by slop-machines takes valuable time that otherwise could be spent more meaningfully by fixing bugs and working on new features. I will try to add links that back up the claims above, but it may take a while. Of course, I see how and where generative tools could be helpful and sometimes I feel tempted to find an acceptable way to use them, but for now the direct and indirect costs far too much outweigh gains. This list has its positive counterpart: Slop-Free (Supposedly) Open-Source Software (not quite complete yet). Also take a look at and give thumbs up to AI Slopfree Software Catalog which contains software dedicated against usage of LLMs. Also, here is a list of some labels that can be added / voted for so they would eventually appear on application pages: Slopware; Slop (LLM) Code; Slop-Source Software; Open-Source Slopware; Contains Slop (LLM Generated) Code.
By Edgars140 appsUpdated

Official Links

What is Scribe?

Vim-flavoured modal editor with the parts a writer actually needs and a few features vim never had. Single static binary, sub-10 ms startup, soft-wrap by default, Claude Code in the editor, syntax highlighting, hunspell spellcheck, Goyo-style reading mode, persistent registers shared across sessions.

Why scribe (and not vim)?

Vim has a thousand features. A writer needs about thirty of them. Scribe is "vim minus 90 % minus the programming subsystem, plus a handful of writer-first niceties":

  • Modal core — hjkl, motions, operators, text-objects, registers, marks, macros, dot-repeat, undo tree.
  • Soft-wrap by default — long prose lines wrap at the pane edge with a continuation indicator. Live resize via SIGWINCH.
  • Claude integration in the prompt — :claude {prompt} runs claude -p over your selection / paragraph / buffer and splices the response back. One u reverses an entire turn. :chat for full interactive sessions.
  • Reading mode — :read (or zr) for Goyo-style centered text, optional Limelight-style paragraph dim. Prose without chrome.
  • Email-mode rendering — .eml files and kastrup compose tempfiles get header / quote-level / signature colors that match kastrup's right pane 1-for-1. Inline email addresses + URLs highlighted everywhere.
  • Syntax highlighting for ~18 source languages plus dedicated HyperList / Markdown / LaTeX renderers via the shared highlight crate. Multi-line block comments and string literals keep their color across line breaks.
  • Spellcheck via hunspell — auto-on for email mode, opt-in elsewhere via :set spell. Configurable language and underline color. ]s / [s navigation, z= suggestions, zg to add to personal dict.
  • Persistent registers — yanks and macros live in ~/.config/scribe/registers.json and update on every yank, so they survive restarts AND share live across concurrent scribe sessions.
  • No LSP / debugger / quickfix / :make — writers don't compile.
  • Block paste that actually pastes a block — Ctrl-v selection lays each row at the same column on consecutive lines. One u reverses the whole thing.