opencode VS Ink

Dax, the creator of OpenCode — an open-source coding agent, of all the people one might expect to disagree — put the case for hand-coding cleanly in a recent interview about Spec-Driven Development:

Pipa is our agent for studio operations at Lunch Pail Labs. She lives in Slack, is powered by E2B sandboxes, and uses OpenCode for the harness.

One reason I liked OpenSpec more than others, such as Kiro and SpecKit, is that OpenSpec is highly portable between coding assistants, codebases and stages of development. I've plugged OpenSpec into all sorts of projects, from infrastructure to Python libraries. I also work on diverse codebases, with a variety of AI friends that OpenSpec supports: OpenCode, Codex and Claude Code.

Beyond the big names, I would also keep an eye on OpenCode and T3 Code. OpenCode is a solid open-source, terminal-first option if you want a model-agnostic agent and bring your own provider setup. T3 Code is interesting for the opposite reason: it gives you an open-source GUI on top of the agents you may already pay for, like Claude Code, Codex CLI, OpenCode, or Cursor.

Brought to you by the infamous creator of OpenCode, who will exfiltrate all your data, then feign ignorance:

https://github.com/anomalyco/opencode/issues/10416

Bubble Tea remains the v0.1 + v0.2 target. The v0.3 cycle starts the cross-framework work: ratatui first, then Textual, then Ink. The registry's per-frame URL prefix already accommodates the second axis; the work is in writing the adapter packs. Components stay copy-paste. The CLI keeps glyph add. The registry shape stays stable.

Terminal UIs are having a renaissance. Bubble Tea in Go, ratatui in Rust, Textual in Python, and Ink in TypeScript have made it normal again to ship a terminal-first product. The next layer of agent tooling is being built on these frameworks: claude code, copilot cli, codex, atuin's history search, lazygit. Every one of those programs reaches for the same set of primitives. A scrollable chat thread. A diff view. A command palette. A status bar. A toast for non-blocking feedback. A spinner that animates while a long-running call resolves.

Ink draws the chat in the terminal — the input box, scrolling text, and key handling — using React so you are not building a TUI from scratch.

perhaps they refer to Claude code being built on top of a React renderer for terminals, Ink https://github.com/vadimdemedes/ink

and is riddled with timeouts and intervals in useffects

This post is the technical writeup: how the file-based router works, the layout engine, and the SSH hosting bit. If you've used Ink (React for the terminal), terminaltui is in the same neighborhood but a step further — it ships routing, layout, and themes as defaults instead of "bring your own React patterns."

There are terminal libraries that do this:

https://github.com/vadimdemedes/ink

Which is what Claude Code CLI uses (or was using?) and it caused many issues such as flickering, thrashing, and latency.

> The reality is different. Most modern Text User Interfaces (TUIs) are often more hostile to accessibility than poorly coded graphical interfaces.

The Claude Code rendering UI is the first place where I realized the TUI is more like a DOS or Borland UI system rather than a command line interface.

I was poking about CLAUDE_CODE_NO_FLICKER=1 setting when I realized what exactly this TUI is, it is layers of stuff showing up on top of each other with terminal codes.

Ended up reading the Ink Terminal implementation of React

https://github.com/vadimdemedes/ink

Fascinating how it ends up looking Wordperfect or Wordstar from the past instead of pixel based graphics.

The usability for a vision impaired user is about the same, though I remember braille pads for DOS tools which work better than all the screen readers which came later.

Yes, the UI is React. Not a web app pretending to be a terminal — actual React components rendered to the terminal via Ink.

The UI layer is built with React and Ink, a library that renders React components to the terminal. Layout is handled by Yoga, the Flexbox engine that also powers React Native. The runtime is Bun rather than Node.js, and the entire application compiles down to a single cli.js bundle at 10.5MB.

Ink is great for simple CLIs. claude-code-kit builds on the same React model but adds: