See why work fits.
Local matching uses your skill profile and related skills to rank opportunities. Your matching profile stays on your machine.
How matching works ↗terminalhire / developers
Bring your judgment.
Put your agents to work.
Find paid coding tasks and open-source issues that fit your stack. Use your own agents and tools, and build a record of work other people accept.
CLI, Claude Code, and your MCP-compatible editor.
~/workexample
terminalhire bounties
PAID TASK
Make webhook retries safe.
acme / payments
Retry the same event.Write once.
- Posted price
- $180
- Your share on acceptance
- $162
- Delivery
- A branch for review
Read the scope. Preview before you claim.
01 / Paid work
A task to finish.
A price up front.
Read what the poster needs, choose a task, and work in your own environment. Payment follows acceptance of the finished work.
- 01
Know what you’re taking.
Preview the task, price and access before claiming. Private-repository work needs the poster’s approval before you get access.
terminalhire claim preview <id> - 02
Work with your own tools.
Start the workspace and bring your editor, agents and test workflow. The posting determines whether you receive a repository or a smaller set of files.
terminalhire claim start <id> - 03
Submit the change.
The poster reviews your branch and can ask for changes. When they accept and payment succeeds, you receive 90% of the posted price.
terminalhire claim submit <id>
What happens after you submit.
We check submitted work in a fresh Google Confidential Space virtual machine. Recorded results show the outcome and any checked evidence of the run environment.
01 / submit
Submitted commit
A separate branch.
An exact revision to check.
A fresh confidential VM
02 / installDependencies inAllowed hosts only
03 / testTests runNo external network
Network disconnects before tests run.
Run finished. VM torn down.
04 / review
Recorded result
- Commit
- Exact revision
- Tests
- Pass / fail counts
- Environment
- Available evidence
The result stays for review.
Process illustration · each submission has its own result.
The submitted commit
The patch becomes a commit on a separate branch. That commit is queued for a run.
A fresh confidential VM
A machine boots for this run, with a venue workload image checked through Google’s attestation.
Install, then cut access
Dependencies install through an allowed list of hosts. The measured tests run without external network access.
Evidence for review
The result records the commit, test command, outcome and available venue evidence. The VM is torn down.
What does Confidential Space add?
Our intake checks Google’s signature, the approved venue image digest, the hardware claims, Secure Boot and disabled debugging before recording Confidential Space evidence. This identifies the run environment; Google does not certify the patch’s correctness. Read each run’s evidence: older runs and local checks can use a different environment. Repository access for the developer is still governed by the posting.
acme / queueexample
Handle an empty batch
Pull request #42src/queue.tsexample diff
18
async function flush(batch) {19
+ if (!batch.length) return;20
await writeBatch(batch);21
}The work has a receipt.
A pull request. A maintainer’s merge. A link to the code.
02 / Open source
Build a record
in open source.
You don’t need a paid task to do work that counts. Find issues on established projects, contribute with your own tools, and earn a merge from someone outside your team.
Terminalhire uses stack fit and signals like maintainer activity and competing PRs to help you choose where to spend your time. The maintainer still decides what gets merged.
Proof of Work links qualifying contributions back to the original pull requests. You choose whether to publish your record.
03 / Your toolkit
Fits the way
you already work.
The useful parts of Terminalhire, together. Install once, then use the surfaces that suit your workflow.
Your workflowYour next piece of work
Your editor
Your agents
Your terminal
TerminalhireFind · claim · contribute
Paid tasksA scope. A price. A change.
Open sourceAn issue. A PR. A contribution.
Stay in your editor.
Use the CLI directly, connect an MCP client, or see matches through the Claude Code and editor surfaces.
Connect your tools ↗See what you’re building with.
Trajectory reads local Claude Code sessions to show your current stack and how it is changing. Review it locally, and choose whether to share a derived view.
Explore trajectory ↗Meet through mutual interest.
Discover opted-in peers. Contact is exchanged when both sides accept an introduction, with chat available in the terminal.
How connections work ↗The working details
Before you
pick something up.
How do payments work?
For first-party paid tasks, the poster saves a card before publishing. When they accept the work and the charge succeeds, you receive 90%; Terminalhire retains 10% and covers payment processing. A saved card is not escrow or a guarantee of payment.
Open-source contributions are generally unpaid. External bounties follow their own platform’s payment terms.
What can I access on a paid task?
The whole repository is the default, with read-only access that includes history and every branch. Your workspace starts at the commit pinned when you claim. A poster can choose a narrower set of files instead. Terminalhire grants no push access; your change returns through the platform on a separate branch.
What rules apply to the submitted patch?
The boundary refuses changes to recognized CI and build files, git internals, and changes to existing package.json scripts or their install and pre/post hooks. A package-lock.json (v2 or v3) or yarn.lock (v1) change is accepted with the package.json change it belongs to, when every new entry comes from the npm registry with its integrity hash. Other lockfiles are refused. Detected network calls, obfuscated code and unclassified manifest changes wait for the poster’s review. New dependencies and new scripts apply unless the poster turns that off.
// paid-task delivery and patch rules
grant the scope the poster chose
flag network calls · obfuscated code
allow new dependencies, unless the poster turns that off
deny .github/workflows · other lockfiles
deny push access, always
// refuse on doubt — the refusal names the file and the hunk
What stays local?
Your matching profile and skill fingerprint stay on your machine. Connected actions such as claiming work, submitting a patch, publishing a profile or accepting an introduction send the data needed for that action.
Read the privacy details ↗Can I still browse job listings?
Yes. Run terminalhire jobs for matched roles. Job search is there when you need it; you can take tasks and contribute without looking for a new job.
Ready when you are
Find your next
piece of work.
Install the CLI, run setup, and start with a paid task or an open-source issue.
curl -fsSL terminalhire.com/install.sh | bash