Open Source

Homelab dashboards tend to be either link boards with no real metrics or full monitoring stacks that feel like overkill. Buoy is the middle ground: one container per node that auto-discovers Docker services, shows system vitals, and polls peer nodes for a fleet view. No database, no build step.

A Sunday backlog on coco that should have eaten the whole day took about an hour. Not because the AI wrote my code, but because steering files and specs meant it already knew the project instead of me re-explaining it every session. Here is what is in mine, and what I left out.

The Pironman5 MAX has a tiny OLED on the front, and the stock software just loops a few system stats on a timer. I replaced it with a single orchestrator page running 15 info screens, 14 animated screensavers, and a health-aware alert mode. Here is how it works.

I rebuilt coco’s interface with a TUI design skill, then needed to show it off. Screenshots and demo GIFs turned out to be their own craft, full of subtle traps. So I built a skill for that too.

The regex-based structural diff extractors landed and worked – then hit a ceiling regex was never going to clear. Here’s how coco’s diff pipeline actually moved onto tree-sitter: sharper structural context for commit messages, a layered regex fallback, lazy-loaded grammars – plus the bonus the same parser bought us, syntax-highlighted diffs in the Workstation.

git-scenarios came together fast because the project it serves, Coco’s TUI git workstation, had very clear testing needs. A couple of weeks after the v0.1.0 extraction it’s now stable at v1.0.0: 32 scenarios, 60+ atoms, five framework adapters, 527 tests across three operating systems. The v1 work wasn’t about features, it was about trust: typed error classes, precondition guards, property-tested determinism, cross-platform CI, and shedding the last of its coco branding.

I have written the same 80 lines of git test setup more times than I want to count. @gfargo/git-scenarios v0.5.0 extracts the helper layer that grew up inside Coco: a registry of named scenarios (mid-merge-conflict, submodule-with-history, mid-bisect, and 8 more), a composable atom API for building your own, and a tool-agnostic CLI that drops any tool into a real repo in a known state.

I got one of those “your key is expiring” emails from Humble Bundle, opened my library, and realized I had no idea how many unclaimed games were sitting there. So I wrote a tool. What followed was a crash course in everything Playwright throws at you when you’re automating a real, bot-averse, React-rendered storefront.

localpress is a CLI tool that processes your WordPress media library locally – compression, WebP/AVIF conversion, AI background removal, and round-trip desktop editing – with no cloud SaaS, no recurring credits, and no plugin required on the WordPress side.

Doorman 2.0 ships Cloudflare WAF support alongside Vercel Firewall, a new .doorman.json config format, and 1,100+ tests backing a production-ready multi-provider firewall CLI.

A look at everything that’s landed in ink-enhanced-select-input on the road to 1.0: a headless hook for custom renderers, multi-select mode, inline search, item groups, scroll indicators, Escape/cancel support, and 133 tests – including a real bug caught by writing edge-case tests for backspace handling in searchable mode.

A small filesystem tweak that turned my open source projects into a single workspace my agents can actually reason about. Nested git repos, a centralized orchestrator, and a documentation loop that finally stays in sync.

After years of building terminal apps and a growing inability to justify my GitKraken subscription, I built a Claude Skill for TUI design. Here’s what’s in it, why I made it, and what I’m planning to build with it next.

A client needed help managing a few VPSes, so I wrote a small bash script. Three rewrites and 21 releases later, it’s Strut: an open-source CLI for deploying Docker stacks anywhere there’s SSH, built agent-first for the way I actually code now.

After building Spec Shaver as a CLI for trimming oversized OpenAPI specs, I kept finding myself wanting a visual way to do the same thing. SpecForge is what came out of that itch: a web app for importing, curating, and exporting OpenAPI specs in the browser.

Hitting OpenAI’s 1MB / 30-operation cap on Custom GPT actions when your real API has 150+ endpoints is maddening. Spec Shaver is the CLI I built to reduce a bloated OpenAPI spec down to the operations that actually matter, while keeping the schema valid.

Fargo Flags is the feature-flag toolkit I wished existed for Next.js: zero infrastructure, type-safe, and small enough to drop into any project. Here’s the design call that shaped it and the trade-off I’m still not sure about.

I built Vercel Doorman because clicking through firewall rules in a dashboard is the kind of thing infrastructure-as-code was supposed to fix. This is what it does, why JSON config beat a DSL, and what I’d change if I started over.

Coco is the AI-powered Git assistant I built because I was tired of writing terrible commit messages at 11pm. The story of how it grew from a one-off script into something I now use daily across every project.

You know those moments during vacation when you should be relaxing, but the creative coding brain just won’t shut off? That was me last week, sitting in an Airbnb with my laptop, a decent WiFi connection, and way too much coffee. The goal? Create my own version of the iconic Matrix digital rain effect – […]

Notes from making tFrogger feel like an arcade classic in a terminal: tuning movement to feel responsive without breaking the per-cell grid, and the legacy config-folder cleanup I should have done sooner.

Explore the joys of building terminal-based card games with a dive into my journey of recreating the classic Memory/Concentration card game using the ink-playing-cards library.

Create a terminal-based Blackjack game with React, TypeScript, and the `ink-playing-cards` card library for a nostalgic yet modern gaming experience.

Upgrade your ink-select-input for seamless vertical and horizontal layouts enabling more intuitive and space-efficient interfaces in your Ink CLI apps

Building Pong as a terminal game with Ink: single-player against an AI paddle, two-player on a shared keyboard, dynamic difficulty as the rally goes. Plus why npx as a distribution channel is underrated for small games.