Open Source

why I built it

Most messengers assume a reliable internet connection and leak metadata about who is talking to whom. I built Hop so devices can route messages directly over Bluetooth, local networks, or transient relays without exposing conversation graphs. The Rust core exposes a C ABI that powers native SDKs across Apple platforms, Go, and Crystal (hop-sdk-apple, hop-sdk-go, and hop-sdk-crystal).

stack

signals

why I built it

Single-prompt agent runs derail because they try to jump straight from idea to code without boundaries. I structured darkrun around assembly-line stations that eliminate risk early, walking from problem frame to verified proof with reviews at each checkpoint. File-backed state keeps the run inspectable and reproducible without depending on a remote database.

stack

signals

why I built it

Coding agents run long tasks that periodically stall on a single confirmation or decision. I got tired of being anchored to a desk terminal just to approve a plan or review a diff. With ompctl, the daemon runs on my dev machine and dials out to a relay, letting me unblock runs and inspect work from my phone.

stack

signals

why I built it

Crystal deserved what Ruby has in rubygems.org and Rust has in docs.rs: one place to find a shard and one place to read its docs. CrystalShards is the registry and CrystalDocs builds every shard's documentation out of band, queued so a slow build never holds up the index. The services scale to zero when nobody is looking.

stack

signals

why I built it

Agent tooling spreads fast and unevenly. Han is the opinionated layer: plugins vetted against how good engineers actually work, so the volume layer inherits judgment instead of replacing it.

stack

signals

why I built it

When agents generate reports, prototypes, or design previews, I needed a safe way to share them with clients without handing raw files to a third-party host. We built Relic so encryption happens on the local machine before upload, putting the decryption key in the URL hash where the server never sees it. The recipient's browser decrypts the ciphertext locally and renders it in an isolated sandbox.

stack

signals

why I built it

Unstructured agent sessions produce sprawling diffs because models wander when they lack process boundaries. We designed the AI-DLC methodology (live at ai-dlc.dev) to break delivery into studios, stages, and quality-gated units. Haiku enforces those gates directly inside Claude Code so agents verify their work before advancing.

stack

signals

why I built it

The connective tissue that makes the rest move faster. Boring on purpose. The part of the toolchain that earns its keep by getting out of the way.

stack

signals

why I built it

A module compiles against its dependencies' declarations, never their bodies, so a build reads less and an agent can read an interface without the whole repository. Edit one module in a 7,207-line project and the rebuild takes 0.13 seconds. Serdar Doğruyol and I maintain it together.

stack

signals