An LLM browser harness in 600 lines, plus three more tools doing one job well

The Lens

Open Design generates design artifacts (websites, mobile apps, decks, docs) by delegating to whichever AI CLI you already have. It detects Claude Code, Cursor, Gemini, OpenCode, Hermes, Kimi, or Codex on your PATH and routes work through them. Apache 2.0. Setup needs Node 24 and pnpm: `pnpm install && pnpm tools-dev run web`. Heavier than a desktop installer but it's a real web app you can deploy yourself. Ships with 31 composable skills (web prototypes, mobile apps, decks, PM specs) and 72 brand-grade design systems sourced from awesome-design-md, including Linear, Stripe, Notion, Apple, and Tesla. Pick this if you already have Claude Code or Cursor and want a design layer over them, or want to host a shared team instance on Vercel. Solo: free. Small teams sharing one CLI key: free plus token bill. Larger teams can deploy it, but they manage infra and prompt quality. The catch: heavier setup than open-codesign, and the multi-CLI delegation means quality depends on whichever agent is installed. If you're not already a CLI agent user, this is the wrong starting point.

The Lens

Floci is a drop-in replacement for LocalStack that's actually free. This matters because LocalStack is sunsetting its free community tier in March 2026. Floci starts in ~24ms, uses ~13 MiB of memory, and the Docker image is ~90 MB vs LocalStack's ~1 GB. It runs on port 4566 (the same port LocalStack uses), so switching requires zero code changes. Built in Java with Quarkus, compiled to a native binary via GraalVM. MIT licensed. Already supports CloudFormation, Step Functions, DynamoDB Streams, Kinesis, Cognito, KMS, Secrets Manager, EventBridge, CloudWatch, API Gateway v2, and more. The catch: it's new and playing catch-up on AWS service coverage. LocalStack has years of edge cases handled. If you use an obscure AWS service, Floci might not emulate it yet. And 'no auth token required' means no telemetry, but also no commercial support if things break.

The Lens

whatcable answers a question macOS hides: what can this USB-C cable actually do? Plug a charger or peripheral into a Mac, and the menu bar tells you the cable's real specs (USB 2.0 vs 5/10/20/40/80 Gbps), its power rating (3A or 5A up to 60W/100W/240W), and why charging might be slower than expected. MIT licensed, free. The data already exists in macOS via IOKit. whatcable surfaces it. No private APIs, no kernel extensions, no daemons. Install via Homebrew (`brew install --cask whatcable`) or grab the signed and notarized .app from GitHub Releases. Apple Silicon only, macOS 14 or later. The "why is my Mac charging slowly" diagnostic is the killer feature. It tells you whether the cable, the charger, or the Mac itself is the bottleneck. This is a niche utility. If you have a drawer of identical-looking USB-C cables and one of them is silently a USB 2.0 charge-only cable, you have already needed this. Free, no paid tier, single-developer maintenance. The catch: Apple Silicon only. Intel Macs use older Thunderbolt controllers that do not expose the PD state and cable e-marker data the app reads.

The Lens

Browser Harness gives LLMs raw access to Chrome through a single WebSocket connection. No abstraction layer, no pre-built recipes, just direct CDP (Chrome DevTools Protocol) control. When the agent encounters something it cannot do, it writes new helper functions mid-task. Self-healing browser automation. The entire codebase is under 600 lines of Python. Connect to Chrome with remote debugging enabled, and your agent can navigate, click, fill forms, extract data, and extend its own capabilities on the fly. From the same team that built the browser-use framework, this is the stripped-down version for agents that need complete freedom. Developers building AI agents that interact with websites: this is the thinnest possible layer between your LLM and a real browser. The free tier at cloud.browser-use.com gives you 3 concurrent remote browsers for testing without managing Chrome instances. The catch: "complete freedom" means no guardrails. Your agent can navigate anywhere, click anything, submit forms. You need your own safety layer if you are pointing this at production accounts.