Getting started
Your code is your résumé. Terminalhire matches you to paid roles from the work you already do. Your profile never leaves your machine — that's true from the first run.
Install
npm i -g terminalhire
terminalhire init
Or the one-liner (pins the current release):
curl -fsSL https://terminalhire.com/install.sh | bash
init walks you through a consented setup: GitHub-derived skill tags (derived
from your public repos and never sent anywhere), optional Claude Code spinner/statusline surfaces,
and optional MCP wiring for other editors.
The commands you'll actually use
| Command | What it does |
|---|---|
terminalhire jobs |
Your matched roles, scored against the job index from a profile that never leaves your machine |
terminalhire contribute |
Feed of credential-building open-source issues, ranked by winnability (on by default) |
terminalhire inbox |
Interactive inbox — connection chats + intro requests |
terminalhire bounties [--priced] |
First-party founder bounties by default; --priced adds scraped paid open-source supply |
terminalhire beta |
Join the invite-only beta (or its waitlist) + feedback to shape the product |
terminalhire refresh |
Pull the latest job index and re-match (also runs ambiently) |
terminalhire mcp --print-config |
Snippets to use terminalhire from any MCP editor |
th works as a short alias everywhere you see terminalhire.
Where it shows up while you work
- Claude Code (terminal): spinner verbs and a statusline with your unread /
intro / match counts — installed as an optional plugin surface during
init. - VS Code, Cursor, Windsurf: a quiet status bar item with the same counts and a hover card of your top matches.
- Any MCP editor (Codex CLI, Gemini CLI, Zed, JetBrains, …): ask your AI assistant for your matches directly — see MCP.
Connect, don't broadcast
Matching with other developers and founders is double-opt-in end to end: nobody sees you until you consent, intros require an explicit yes from both sides, and chat is end-to-end encrypted. Details in Privacy architecture.