In the AI-agent era, Markdown is becoming the control surface for software work: instructions, specs, review notes, implementation plans, and context that guide agent CLIs.
But Markdown editing still breaks the terminal flow. GUI editors pull you out of the shell. Terminal editors usually lack table and diagram tools. A quick plain-text diagram often means opening a browser-based ASCII diagrammer or a dedicated diagram drawing app.
zago is built for that shift: a lean terminal Markdown forge that keeps prose
editing, pipe tables, local document links, headings, text diagrams, CJK-aware
text tools, and small automation macros in the same plain-text flow, whether
the file is on your laptop or on a server over SSH.
- AI-agent users who write Markdown instructions, specs, notes, and review context from the terminal.
- Markdown writers who want prose, headings, links, tables, and diagrams in one terminal tool.
- Technical writers who prefer plain-text documents that remain readable in Git diffs, SSH sessions, pull requests, and README files.
- People drawing text diagrams who do not want to leave the document just to open a diagramming app.
- CJK and emoji perfectionists who need terminal display width to be correct when boxes, status-icon tables, rulers, and wrapped prose are involved.
- Keyboard-first document builders who like nano-style editing, but want a sharper toolbox for Markdown-era writing.
- Markdown-first editing: write prose, jump through local document links, navigate headings, and keep README-style documents close to their final form.
- Table-aware editing: format Markdown pipe tables, move between table cells, and edit table content without breaking borders.
- Plain-text diagramming: draw boxes, arrow connector lines, fills, and table layouts directly in the buffer.
- Text processing for writers: count chars, words, lines, CJK chars, and emojis; normalize CJK/ASCII spacing; transform selected text between scripts.
- Unicode-aware layout: CJK and emoji such as ✅, ❌, and
⚠️ keep boxes, tables, fills, rulers, and connector lines aligned. - Modeless typing & dual spatial modes: Ordinary typing always inserts text
directly. Press
M+Vto toggle between standard text stream mode and 2D Canvas Mode for freeform grid navigation and block editing. - Nano-compatible controls:
^Osave,^Xexit,^Wsearch,M+Wcopy,^Kcut,^Upaste,^Jjustify,^Zundo. - Dynamic softwrap, visual paragraph reflow, syntax highlighting, and Nano
.nanorcsyntax loading. - Multi-buffer editing, file auto-reload.
- Natural command prompt: press
Escand run editing commands such asBOX 30 4,LINE,FILL "hi, orREPEAT 5 [...]. - Lightweight automation: reuse command sequences with variables, loops, and procedures when editing becomes repetitive.
- macOS 14.0+ or Linux
- Swift 6.0+
- VT100 / ANSI-compatible terminal
Install from the Homebrew tap:
brew tap zonble/zago
brew tap --trust zonble/zago # allow this third-party tap
brew install zago
zago notes.txtIf Homebrew refuses to install from an untrusted third-party tap, run the brew tap --trust zonble/zago line and install again.
On Linux, the Homebrew formula builds zago with Homebrew's swift package. Without Homebrew, install Swift 6 from your distribution or Swift.org and use the source build commands below.
Install with Mint:
mint install zonble/zago
zago notes.txtOr run without installing:
mint run zonble/zago notes.txtBuild from source:
git clone https://github.com/zonble/zago.git
cd zago
swift build -c release
.build/release/zago notes.txt
.build/release/zago notes.txt --wrap 80
.build/release/zago notes.txt --ruler
.build/release/zago --init # optional: create a starter ~/.zagorcFor early testers, the simplest source install path is:
git clone https://github.com/zonble/zago.git
cd zago
./build.sh
zago --versionThis installs zago to /usr/local/bin/zago by default. To install under your home directory:
PREFIX="$HOME/.local" ./build.sh
export PATH="$HOME/.local/bin:$PATH"See Release & Preview Builds for smoke tests, known limitations, and what to include in bug reports.
zago provides two complementary spatial editing modes. In both modes, typing remains modeless and inserts characters directly:
- Text Mode (Default): Standard linear text editing for prose and code. Selections follow linear text streams.
- Canvas Mode (
M+V): Unlocks 2D virtual space navigation beyond line ends. Supports 2D rectangular block selection (Shift+Arrows), block copy (M+W), block cut (^K), and block paste (^U) without distorting surrounding text layout.
For details on selection rules and clipboard separation, see Mark, selection, and canvas behavior.
zago is still a text editor. The diagram tools sit on top of ordinary prose editing rather than replacing it:
- Linear text selection in Text Mode and Table Mode, including
Shift+ArrowandShift+Home/Shift+End, with selected text replaced by typing. - Paragraph justification (
^J) for mixed CJK and Latin prose, using display width instead of byte or scalar counts. - Selection-based text transforms from the Tools menu: Traditional/Simplified Chinese conversion, Latin/Hiragana/Katakana/Romaji transliteration, and CJK/ASCII spacing normalization.
- Text counts from the Tools menu. With a selection,
Word Countreports that selection; without a selection, it reports the whole document. The status includes chars, words, lines, and only shows CJK chars or emojis when present. - Optional sub line numbers for fixed-width prose drafting: when a wrap column is set, long physical lines can show visual-row numbers and paragraph character counts.
- Document link navigation with
M+Ofor local Markdown, Org, reStructuredText, and AsciiDoc links. - Heading navigation and outline picker for Markdown, Org, reStructuredText, and AsciiDoc documents.
The command language is Editor LOGO. Commands read like direct editing actions, but they can still be combined with variables, loops, and procedures when the work becomes repetitive.
BOX 30 5
MOVE HOME
TYPE "# "
MOVE END
The same language is available from the command prompt, key bindings, and startup configuration. Variables and procedures stay available throughout your editing session, so they can live for the lifetime of the buffer session.
Create a numbered list:
REPEAT 5 [ TYPE :# ". List item" NL]
or
FOREACH (ISEQ 1 5) [TYPE ? ". List item" NL]
or
MAKE "i" 1 REPEAT 5 [ TYPE :i TYPE ". List item" MOVE DOWN MOVE HOME MAKE "i" (:i + 1) ]
Define and reuse an editor-local procedure:
TO TITLE :text
BOX :text CENTER ROUND
END
TITLE "Release Notes"
Draw and fill a canvas box:
DRAWBOX 30 4 ROUND
GOTO 2 2
FILL "hi
╭────────────────────────────╮
│hihihihihihihihihihihihihihi│
│hihihihihihihihihihihihihihi│
╰────────────────────────────╯
Draw a small plain-text architecture diagram:
DRAWBOX 18 3 "client" CENTER
GOTO 3 11
VLINE 3
GOTO 5 1
DRAWBOX 18 5
GOTO 6 2
TYPE " server "
GOTO 7 1
LINE 18
GOTO 8 2
TYPE " database "
┌────────────────┐
│ client │
└─────────┬──────┘
│
┌─────────┴──────┐
│ server │
├────────────────┤
│ database │
└────────────────┘
zago operates both as an interactive TUI editor and as a headless CLI diagram/table generator.
Open one or more files in the terminal TUI editor:
zago notes.txt
zago file1.txt file2.txt --wrap 80 --rulerExecute LOGO scripts or inline LOGO code from the command line, render the canvas to a text buffer, and print the resulting ASCII output directly to stdout:
# Execute inline LOGO code and print output
zago -e "BOX 20 4; MOVE DOWN MOVE RIGHT; FILL \"Hello World\""
# Execute a LOGO script file and redirect output to a file
zago -s myscript.logo > diagram.txt
# Pipe generated diagram directly to clipboard
zago --run generate_architecture.logo | pbcopy| Option | Flag | Description |
|---|---|---|
files |
File(s) to open in interactive editor mode. | |
-w, --wrap <col> |
Specify softwrap column width (e.g. 80). | |
-r, --ruler |
Display WordStar-style ruler bar above viewport. | |
-e, --eval <code> |
Execute inline LOGO code in headless mode and print to stdout. | |
-s, --run, --script <file> |
Execute a LOGO script file in headless mode and print to stdout. | |
--init |
Generate default ~/.zagorc configuration file. |
|
--syntax <true/false> |
Enable or disable syntax highlighting. | |
--lang <en/zh_TW> |
Set interface language. |
You probably don't.
In agent-facing Markdown, the source is the interface. AI agents read the
Markdown itself; they do not need a rendered HTML preview. zago focuses on
making that source easier to write, shape, and maintain.
For the same reason AI agent CLIs exist: the terminal is still the shortest path between code, files, tools, and remote machines.
The features I want are not just Markdown syntax helpers. They touch the editor's interaction model: Text Mode and Canvas Mode, table-cell editing, rectangular canvas blocks, LOGO commands, selection-based text tools, status lines, menus, and key bindings.
In a powerful plugin ecosystem, that kind of opinionated workflow can easily
fight the host editor, existing user habits, and other plugins. zago keeps the
surface smaller so these pieces can be designed as one coherent Markdown writing
flow.
因為我不會。
Yes. BTW, I am an 80s kid. :p
Also, LOGO is still a pretty good little language for movement, repetition, shapes, and text macros.
Type spaces over it, or use Canvas Mode block cut when the shape is rectangular.
- Editor basics
- Search behavior
- Mark, selection, and canvas behavior
- Editor LOGO command language
- Configuration and key bindings
- Pen mode and turtle drawing
- Diagram snippets & menu rules
- Homebrew tap
- Release & preview builds
- Changelog
Run swift test.
MIT License. Copyright (c) 2026 Weizhong Yang a.k.a. zonble.
Note: The name zago stands for "zonble's nano + LOGO".