HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
charmbracelet
glow
Go2019–2026
charmbracelet / glow

glow

Render markdown on the CLI, with pizzazz! 💅🏻

34Distinct people
43Mentions
0Explicit recommenders
28KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Render markdown on the CLI, with pizzazz! 💅🏻

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year43 dated mentions

Observed mentions: 2019-12-27 22:32:19 UTC to 2026-09-11 12:50:29 UTC.

02468102019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 3 submissions, 5 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC321
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC624
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC606
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC909
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC835
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC918

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
Glow Render markdown on the CLI, with pizzazz! What is it? Glow is a terminal based markdown reader designed from the ground up to bring out the beauty—and power—of the CLI. Use it to discover markdown files, read documentation directly on the command line. Glow will find local markdown files in subdirectories or a local Git repository. Installation Package Manager # macOS or Linux brew install glow # macOS (with MacPorts) sudo port install glow # Arch Linux (btw) pacman -S glow # Void Linux xbps-install -S glow # Nix shell nix-shell -p glow --command glow # FreeBSD pkg install glow # Solus eopkg install glow # Windows (with Chocolatey, Scoop, or Winget) choco install glow scoop install glow winget install charmbracelet.glow # Android (with termux) pkg install glow # Ubuntu (Snapcraft) sudo snap install glow # Debian/Ubuntu sudo mkdir -p /etc/apt/keyrings curl -fsSL https://repo.charm.sh/apt/gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/charm.gpg echo "deb [signed-by=/etc/apt/keyrings/charm.gpg] https://repo.charm.sh/apt/ * *" | sudo tee /etc/apt/sources.list.d/charm.list sudo apt update && sudo apt install glow # Fedora/RHEL echo '[charm] name=Charm baseurl=https://repo.charm.sh/yum/ enabled=1 gpgcheck=1 gpgkey=https://repo.charm.sh/yum/gpg.key' | sudo tee /etc/yum.repos.d/charm.repo sudo yum install glow Or download a binary from the releases page. MacOS, Linux, Windows, FreeBSD and OpenBSD binaries are available, as well as Debian, RPM, and Alpine packages. ARM builds are also available for macOS, Linux, FreeBSD and OpenBSD. Go Or just install it with go: go install charm.land/glow/v3@latest Build (requires Go 1.21+) git clone https://github.com/charmbracelet/glow.git cd glow go build The TUI Simply run glow without arguments to start the textual user interface and browse local. Glow will find local markdown files in the current directory and below or, if you’re in a Git repository, Glow will search the repo. Markdown files can be read with Glow's high-performance pager. Most of the keystrokes you know from less are the same, but you can press ? to list the hotkeys. The CLI In addition to a TUI, Glow has a CLI for working with Markdown. To format a document use a markdown source as the primary argument: # Read from file glow README.md # Read from stdin echo "[Glow](https://github.com/charmbracelet/glow)" | glow - # Fetch README from GitHub / GitLab glow github.com/charmbracelet/glow # Fetch markdown from HTTP glow https://host.tld/file.md Word Wrapping The -w flag lets you set a maximum width at which the output will be wrapped: glow -w 60 Paging CLI output can be displayed in your preferred pager with the -p flag. This defaults to the ANSI-aware less -r if $PAGER is not explicitly set. Styles You can choose a style with the -s flag. When no flag is provided glow tries to detect your terminal's current background color and automatically picks either the dark or the light style for you. glow -s [dark|light] Alternatively you can also supply a custom JSON stylesheet: glow -s mystyle.json For additional usage details see: glow --help Check out the Glamour Style Section to find more styles. Or make your own! The Config File If you find yourself supplying the same flags to glow all the time, it's probably a good idea to create a config file. Run glow config, which will open it in your favorite $EDITOR. Alternatively you can manually put a file named glow.yml in the default config path of you platform. If you're not sure where that is, please refer to glow --help. Here's an example config: # style name or JSON path (default "auto") style: "light" # mouse wheel support (TUI-mode only) mouse: true # use pager to display markdown pager: true # at which column should we word wrap? width: 80 # show all files, including hidden and ignored. all: false # show line numbers (TUI-mode only) showLineNumbers: false # preserve newlines in the output preserveNewLines: false Contributing See contributing. Feedback We’d love to hear your thoughts on this project. Feel free to drop us a note! Twitter The Fediverse Discord License MIT Part of Charm. Charm热爱开源 • Charm loves open source
Read the full README on GitHub

What Hacker News says

6 sources
My open source command line tool aider [0] is specifically for this use case of working with GPT on an existing code base. Let me know if you have a chance to try it out. Here is a chat transcript [1] that illustrates how you can use aider to explore an existing git repo, understand it and then make changes. As another example I needed a new feature in the glow tool and was able to make a PR [2] for it, even though I don't know anything about that codebase or even how to write golang. [0] https://github.com/paul-gauthier/aider [1] https://aider.chat/examples/2048-game.html [2] https://github.com/charmbracelet/glow/pull/502
In Tips for programmers to stay ahead of generative AI
This looks super interesting, thanks for sharing. I like that you're exploiting the new functions API to give GPT agent-style access to explore a codebase. I have played with that previously with gpt-3.5 and plan to do some more experiments with gpt-4 someday soon. I am also working on an open source CLI tool in this space [0]. I've taken a different approach, more focused on chatting with GPT to have it edit the code in your local git repo. But my tool also provides GPT with a semantic map of your repo and the ability to ask to see particular files, etc. I use it to answer questions about unknown codebases all the time, and then start asking it to make changes. I have a chat transcript that illustrates that here [1]. As another example I needed a new feature in the glow tool and was able to make a PR [2] for it, even though I don't know
Read the rest
anything about that codebase or even how to write golang. Also, there's a small discord [3] where a few of us working on "AI coding tools" have been sharing ideas. You might be interested in joining the conversation over there. [0] https://github.com/paul-gauthier/aider [1] https://aider.chat/examples/2048-game.html [2] https://github.com/charmbracelet/glow/pull/502 [3] https://discord.gg/fHcgCRGu
In Show HN: Open-source code search with OpenAI's function calling
Yup, those seem to be the key challenges. I've been making good progress on them, but there's plenty more work to do! On the topic of "AI-generated PRs", I used my tool to file a PR to the `glow` CLI tool. I don't know the go language, so I had my tool `aider` add the feature I needed. I mostly use glow to preview README.md for GitHub, so I wanted it to render line breaks like GitHub does. https://github.com/charmbracelet/glow/pull/502 I've also been able solve a couple of github issues that were file by users by just pasting the issue into my tool... it fixed itself. Links below: https://github.com/paul-gauthier/aider/issues/13#issuecommen... https://github.com/paul-gauthier/aider/issues/5#issuecomment...
In Show HN: gpt-engineer – platform for devs to tinker with AI programming tools
The problem I have with AsciiDoc (AD) and Markdown (MD) is that they are too effective (in the best way)! Follow my reasoning for a moment, please... I was reviewing a command-line MD reader today. I think it was the nth time I've looked it over. It's called glow : https://github.com/charmbracelet/glow I always come to the same conclusion. I don't need it. I don't need to remember to use (yet) another command line program to read MD or perform a very specific (and non-vital) function. The reason is that MD and AD are so very easy to read. They are too effective at their jobs. They aren't like HTML tags that get in the way of the text. You barely even notice MD/AD in most(?) cases. Text plus MD/AD are incredibly easy to read without a 3rd-party program "rendering" the results. Having said that... the only time I got really excited about MD
Read the rest
/AD was when there was a post about Textual Markdown : https://news.ycombinator.com/item?id=34028765 It wasn't that the "rendered" text looked great (it looked beautiful, btw) but I could see 'Textual Markdown' turning into a command-line, online browser just for MD text! Think about that... I even thought about how great it would be if the GeminiSpace folks : https://en.wikipedia.org/wiki/Gemini_(protocol)?useskin=vect... : embraced MD/AsciiDOC instead of their limited markup language. It's exciting to think of MD/AD making themselves an alternative lightweight tagging system on the web. Exciting to think about a lightweight web in general - no tracking, adware, tons of JS, etc... Exciting to think about a bunch of browsers growing out of this (ie; you don't need billions/yr to support MD/AD browsers) - from full-blown GUIs to, well... "Textual-Markdown". Anyway... MD/AD would be great if it grew beyond offline use. For offline use only... you really don't need rendering. Maybe it helps a bit with really long files but otherwise...
In I wish Asciidoc was more popular

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.