Beta — Founding Contributors & feedback
Terminalhire runs an invite-only beta. Founding Contributors help shape the core while it's still baking, and get a direct line to the person who ships the fixes. Like everything else, joining is opt-in and consent-first — nothing about you crosses the wire until you type "yes".
Join the beta
terminalhire beta # opt-in wizard: the deal, then a typed-yes to join
The wizard is a short, keyboard-driven flow: it explains the two asks and the four rewards, then asks you to type "yes" to join, plus a separate (default-off) choice about whether to be listed publicly as a Founding Contributor. On success you get your Founding Contributor number.
Joining sends only your public-listing choice, under the session you linked with
terminalhire link. If this terminal isn't linked yet, the wizard points you at
terminalhire link and sends nothing. The beta is allowlisted — your GitHub
login has to be on the invite list. If it isn't yet, you're placed on the
waitlist instead; the wizard tells you which of the two happened. Re-running
terminalhire beta later is a pure status re-check — it sends nothing new, and
picks up your membership the moment an invite lands.
Send feedback
terminalhire feedback # structured feedback, straight to the founder
feedback asks a few short questions — what you were trying to do, expected vs.
actual, quick 1–5 ratings (all skippable), and what almost made you quit — then
shows you the exact payload before anything is sent and waits for a typed
"yes". Everything is what you type; the only things auto-attached are your CLI
version and OS — no fingerprint, no telemetry, no scraping of your commands.
What's local vs. what crosses the wire
| Stays on your machine | Crosses the wire (only after a typed "yes") |
|---|---|
| Your profile, matches, git/command activity | Your public-listing choice (on join) |
Anything you don't type into feedback |
The feedback you type + your CLI version + OS |
Feedback and joining are the only beta actions that send anything, they're both gated behind an explicit typed consent, and both go under your linked web session — never your GitHub token. See Privacy architecture for the full picture of what stays local across every surface.