Загрузка видео...
Не удалось загрузить видео
The libghostty Zig and C API as well as the Ghostling demo application have all been updated to support "effects", or the ability for libghostty to now handle side effects (bell, titles, etc.) and responses (size reports, etc.). Here's a devlog about it. Links to examples below: Zig PR:... show more
43,568 просмотров • 7 месяцев назад •via X (Twitter)
Комментарии: 14

YouTube:

don't let @kitlangton hear that libghostty can handle "Effect"

I’m working on an agent multiplexer using libghostty to store terminal state in the backend (like zmx). I have a few UI/layout issues for Codex when reattaching. Excited to try this out!:

Love it! was using it as reference for making it work on harmonyos for fun ><

zig = like

Legend!

awesome stuff!

Nice work. libghostty is coming together quite nicely!

Remember when libghostty launched without any effect handlin? Complete circle now lol

this is so fricking awesome. team is killing it

what do you use to record these videos?

Handling side effects and responses in the terminal layer is a bigger unlock than it sounds. Once agents can rely on bells, titles, and size reports behaving consistently, the surrounding tooling gets much easier to make observable and reproducible.

An online AI said you might be able to help me expand a project I started on Google blogger. I’m not asking you to read this, but ask your AI what we could learn from each other, if more people copied what I’m doing.

Defining clear boundaries for API-handled 'effects' is critical. That low-level architectural clarity is often the unseen foundation for preventing future chaos. What did you prioritize in scoping these additions?
