// the find
unkn0wn-root/resterm
Terminal API client for HTTP/GraphQL/gRPC with support for SSH tunnels, WebSockets, SSE, Workflows, Profiling, OpenAPI, Kubernetes port-forwarding and headless API.
Resterm is a keyboard-driven TUI API client for developers who refuse to leave the terminal and don't want a SaaS tool holding their API keys. It covers HTTP, GraphQL, gRPC, WebSockets, and SSE with SSH tunnels, Kubernetes port-forwards, multi-step workflows, and a headless Go API — all local, no account required. The target is backend engineers who currently juggle curl, grpcurl, and wscat in separate windows.
The headless package is a real differentiator: the same execution engine that powers the TUI is exposed as an embeddable Go API, so you can drive request execution from CI pipelines or internal tooling without shelling out or screen-scraping. Requests live in plain .http files, which means they belong in git, diff cleanly in PRs, and aren't hostage to a proprietary export format. SSH tunnel and Kubernetes port-forward are built in natively — you don't need a separate terminal tab running kubectl port-forward while you debug. OAuth 2.0 with PKCE is handled properly: it spins up a local callback server, captures the redirect, and caches the token — most CLI tools either skip this or do it wrong.
RestermScript is a custom expression language that sits alongside JavaScript hooks, giving you two scripting systems where one would do — and the custom one has zero external tooling, no debugger, and no community knowledge base to Google against. The glibc 2.32+ requirement for pre-built Linux binaries silently breaks on Ubuntu 20.04 LTS (ships with 2.31), which is still widely deployed; the README buries this in a NOTE. The feature surface is extremely wide for what looks like a small team: gRPC streaming, WebSocket scripting, OAuth, SSH tunnels, K8s port-forwards, profiling, tracing, and a custom language are each individually complex maintenance burdens, and rough edges in any one of them won't surface until you actually need that feature. The star-to-fork ratio (1787 stars, 48 forks) suggests users are watching rather than contributing, which is a fragility signal — if maintainer interest fades, this goes dark quickly.