The glamourous AI coding agent for your favourite terminal

A lightweight language model chat service accessible through HTTP, SSH, DNS, and API. One binary, no JavaScript, no tracking.

# Web (no JavaScript)
open https://ch.at

# Terminal
curl ch.at/?q=hello             # Streams response with curl's default buffering
curl -N ch.at/?q=hello          # Streams response without buffering (smoother)
curl ch.at/what-is-rust         # Path-based (cleaner URLs, hyphens become spaces)
ssh ch.at

# DNS tunneling
dig @ch.at "what-is-2+2" TXT

# API (OpenAI-compatible)
curl ch.at/v1/chat/completions

Multi-protocol service monitoring system with real-time alerts and web dashboard. Supports HTTP/HTTPS, TCP and gRPC monitoring with Telegram notifications.

Visualize real time plots of your Go program runtime metrics, including heap, objects, goroutines, GC pauses, scheduler and more, in your browser.

TreeView is a feature-rich Go library for displaying and navigating tree structures in the terminal. TreeView has full Bubble Tea and Lipgloss support, allowing you to build glamorous, interactive terminal applications.

Enhanced reflection for Go using DWARF debug information to extract function parameter names, enabling automatic struct generation and semantic function calls.

A principled CORS middleware library for Go, designed to be both easier to use and harder to misuse than existing alternatives.

Minimal, customizable, and neofetch-like weather CLI inspired by rainy, written in Go

Go implementation of JSON Web Tokens (JWT).

- Docker v2: simpler, multi-arch ready via buildx (alpha)
- Image Attestation: digest files for verifying Docker builds
- Makeself: self-extracting installer support
- Go 1.25: updated Go compatibility
- Version Sorting: smarter semantic tag handling
- New Features & Fixes: bun targets, templating, retry logic, SBOM, various bug fixes and enhancements

A few weeks ago Anton Zhiyanov published the blog post Expressive tests without testify/assert. It's a good and well thought-out post, and I recommend giving it a read if you haven't already. In the post, Anton makes the argument for not using packages like testify/assert for your test assertions, and instead creating your own minimal set of assertion helpers to use in your tests. In fact, so minimal that there are only 3 helpers he uses: AssertEqual, AssertErr and AssertTrue.