Coding

Pragmatic notes on developer tools, languages, and workflows. Shortcuts, tricks, and lessons from actually shipping code.

An old open terminal sealed in a specimen jar beside a closed steel monolith labeled agy, with a developer crossing a bridge between them.

Gemini CLI Is Dead: Migrating to Antigravity CLI in 2026

Google shut down Gemini CLI on June 18, 2026, pushing free, Pro, and Ultra users onto the closed-source, Go-based Antigravity CLI . You can keep the open-source Gemini CLI running with a paid API key, but its separate quota pool is gone. Enterprise and Code Assist Standard licenses still work unchanged.

Key Takeaways

Gemini CLI stopped serving free, Pro, and Ultra accounts on June 18, 2026.
Its replacement, Antigravity CLI, is a closed-source Go binary, not open TypeScript.
You can still run Gemini CLI by feeding it a paid Gemini API key.
The catch: agy shares one usage pool, so quotas drain much faster.
Enterprise and Code Assist Standard licenses keep working unchanged.

What happened to Gemini CLI?

On June 18, 2026, Gemini CLI and the Gemini Code Assist IDE extensions stopped serving requests for free, Google AI Pro, and Ultra personal accounts. The Google Developers Blog announcement confirmed the cutoff and named the replacement: Antigravity CLI, run with the command agy.

Build a CLI Dashboard with Go and Bubble Tea

The Charmbracelet Bubble Tea framework lets you build live terminal dashboards in Go using the Model-Update-View pattern from Elm. Pair it with Lip Gloss for styling and Bubbles for ready-made widgets. You get live panels, key navigation, and flex layouts. It all ships as one binary with zero runtime dependencies.

Terminal dashboards fill a niche that classic CLIs and web apps both miss. Think of a monitor that runs over SSH on a headless box. Think of a database explorer that starts in milliseconds with no browser. Think of a log viewer your ops team can reach with no auth layer to set up. These are the use cases where TUI dashboards shine. Bubble Tea now sits at v2 with over 41,000 GitHub stars and more than 18,000 apps built on it. It has become the go-to framework for this kind of work in Go.

Three racing robots on parallel tracks, one chrome and sealed, one open-framed with swappable engine modules, one screen-headed on wheels

OpenCode vs Claude Code vs Cursor: Model-Agnostic Verdict

OpenCode, Claude Code, and Cursor solve the same job three different ways. On one production-codebase test, Claude Code finished 45% faster while OpenCode wrote 29% more tests, and Cursor is the IDE-native option neither benchmark page even mentions. The real winner depends on the model you run and the budget you keep.

Key Takeaways

Claude Code is faster and polished; OpenCode runs any model you want.
On one test Claude finished 45% faster, but OpenCode wrote 29% more tests.
Cursor is the IDE pick; the other two live in your terminal.
Reddit’s verdict: the better tool depends on which model you run.
OpenCode plus a local model can cut your coding-agent bill to near zero.

What is the difference between OpenCode, Claude Code, and Cursor?

These three tools split along two lines: who picks your model, and where the agent lives. Claude Code is the managed option. It works out of the box. The catch is that it ties you to Anthropic models like Sonnet, Haiku, and Opus. It runs in your terminal and mostly “just works” with no setup.

Seven robotic hands reach for a glowing key, three chained to vendor vaults, two holding open rings of swappable model keys, two on short routed leashes, beside a cost-balance scale

Best AI Coding Agents in 2026: Cost, Autonomy, and Lock-In

The best AI coding agent in 2026 comes down to two numbers most reviews skip. The first is real cost per completed task. The second is how locked in you are to one vendor’s models. Get those two right and the rest is preference. Get them wrong and you either overpay every month or hand a single vendor control of your roadmap. This compares seven agents on exactly those axes: Claude Code, Codex CLI, Gemini CLI, Cursor, OpenCode, Pi, and GitHub Copilot.

Gleam for Erlang Developers: Type-Safe Language for the BEAM VM

Gleam is a statically-typed functional language that compiles to Erlang BEAM bytecode and JavaScript. It gives you OTP’s fault tolerance and distribution with Hindley-Milner type inference - the same type system family as Haskell and OCaml - without making you leave the BEAM ecosystem you already know. As of April 2026, the latest stable release is v1.15.3, and the ecosystem has matured to include a full HTTP server stack (Wisp + Mist ), database drivers, and a built-in language server. If you write Erlang or Elixir professionally, Gleam is worth your attention.

Building a Language Server Protocol Extension from Scratch

The Language Server Protocol (LSP) lets you write language smarts once and use them in every editor. You build one server that handles autocomplete, diagnostics, hover docs, and go-to-definition. Then you plug it into VS Code, Neovim, Helix, Emacs, or anything else that speaks LSP. This walkthrough shows how to build an LSP server in TypeScript for a custom .config file format, from setup through multi-editor support.

What the Language Server Protocol Actually Is

Before LSP, editor support for a language meant writing a separate plugin for every editor. Want Python support? Write a VS Code extension, an Emacs mode, a Vim plugin, a Sublime plugin. Each one redoes parsing, diagnostics, and completion from scratch. With N editors and M languages, that’s N*M plugins to maintain.