Pinned Tweet
Today I'm announcing Canario, a new terminal for macOS.
It uses Rio under the hood 🐤
Spaces with their own colors (⌘1–9), splits, a ⌘K command bar, live tab previews, session restore, and a floating quick terminal on ⌥⌘T.
macOS only for now, Linux and Windows are coming.
The Chrome dinosaur game running in a terminal, with every sprite drawn through Glyph Protocol. No patched font, no images, no sixel.
This is a port of VT-Rex by James Holderness, which was written for DEC VT terminals and ships its graphics as a DECDLD soft font. In this version the same 10x16 bitmap font is converted to vector outlines at startup and registered with the terminal over Glyph Protocol. The dinosaur, cactuses, clouds and score are all just characters in terminal cells.
How it works:
- At startup the game asks the terminal whether it supports Glyph Protocol.
- Each glyph is sent as an OpenType glyf outline and mapped to a private codepoint (U+100000 and up).
- Play-area glyphs span two cells; the score line uses one-cell versions of the same outlines.
- Every frame is composed in memory and written out as plain text.
Running here in Rio terminal.
Source (this port): github.com/raphamorim/vtrex-…
Original VT-Rex: github.com/j4james/vtrex
Glyph Protocol spec: github.com/raphamorim/rio/bl…
Introducing Glyph Protocol: rapha.land/introducing-glyph…
Rio terminal: rioterm.com
#terminal #glyphprotocol #rioterm #cpp
13
619
Rio (rio-vt included) terminal now supports OSC 7501 program status.
Canario just got updated. It will show up some custom icons based on the program that you are running.
Glyph Terminal Protocol + Boo demo (Nov 2026)
There’s one thing about terminals that has always bothered me: to get your favorite editor, prompt, or TUI to render nicely, you are almost always forced to install a patched font.
You know the drill. You open a fresh terminal, pull up your editor, and half of the UI is replaced by little rectangles: the infamous tofu. The fix is to go download a Nerd Font, or Powerline, or some other patched set, and switch your terminal font to it. A font that is often well above 10MB in size. All of that, just so you can render one icon, or maybe a handful of them.
This is messed up. The bundle is huge, the workflow is clunky, and the application author has no way to ship the glyph they actually want. They can only hope the user has installed the right font, with the right version, mapping the right codepoints.
So I decided to do something about it.
Glyph Protocol is a terminal protocol that lets applications do two things:
1. Register custom glyphs with the terminal directly, at runtime. The application picks a codepoint in the Unicode Private Use Area (where Nerd Fonts, Powerline, and every other icon convention already live), ships the vector outline, and emits the codepoint when it wants the glyph rendered.
2. Query the terminal to ask whether a given codepoint is covered by a system font, by a registration in this session, by both, or by neither.
more about it rapha.land/introducing-glyph…
231
Migration of tsgolint backend to "oj lint" (uses @voidzerodev's tsrs_lint under the hood)
Can't take any credit for it. OJ uses the tsrs team's awesome work as a library, and you can use it without OJ too (tsrs --lint).
1
16
1,035
we are half way through migration from Vite to OJ.
HMR update latency, server to editor, per hour (p50 / p90).
2
24
1,396
My talk at @golab_conf last October is now available on Youtube.
I recommend if you love Charm, Go, WASM, Compilers or even JavaScript.
Raphael Amorim retweeted
GM Builders!
Omarchy, AI, Open source, in the open, health and fitness - love to hear from you!
What are you working on?
It was a huge relief to get Terminal Delight 0.5.0 off my plate with the very recent Rio release from @raphamorim
The infinite backlog is SCREAMING though:
- Can we get Rio Terminal into Omarchy as a default option with the big dogs?
- Improvments to the Omarchy CRT Plugin
- Omarchy slopoganda is too much to keep up with!
migrated tsgo to oj typecheck (tsrs under the hood)
part of this work will eventually be migrated to oj dev-typecheck (more info soon)
Rio terminal v0.5.29 released github.com/raphamorim/rio/re…
Thanks everyone that contributed and @aymanbagabas for 2 important fixes!
Announcing today: OJ typecheck
Now you can run "oj dev <path> --typecheck". Agents (and you) run "oj typecheck", which asks the running dev server and answers from its warm checker.
How it works:
1. It's built on tsrs from the Oxc project.
2. The checker runs in its own OJ process beside the dev server, so a crash in it never takes the server down. The dev server's watcher forwards every change to it.
3. After an edit it re-checks only the files the edit affects, like "tsc --watch". Between checks it records each file's exported types in the background, after a short quiet window, so a burst of edits is handled once.
4. With no dev server running, "oj typecheck" checks from scratch in its own process.
5. Typecheck thread only starts after the first serve, to avoid affecting cold starts and reuse the app metadata.
In a big app:
- Full check: 11.5s vs 14.4s for tsc, with a third of the CPU and 3.2 GB vs 10.5 GB of memory.
- Re-check after an edit: about 1.1 s, down from about 10s.
- An edit that changes a component's exported types: about 8s, since every file that imports it is re-checked.
- Asking again with nothing changed: 0.04s.
It's an experimental feature so anything lemme know.
2
11
673













