100% free · open source · no sign-in · no telemetry · local-first
Clinch
A terminal built for Agentic Engineering.
Every session auto-resumes on restart. Self-adapting UI. Quick-response and action buttons. One-click session transfers between Claude Code and Codex.
Install with Claude Code or Codex
Paste this prompt into your coding agent:
Install Clinch Terminal from https://github.com/elliot-ylambda/clinch-terminal. Follow the official install instructions, review the installer source, and verify the release before installing.
Or paste this directly into your terminal:
curl -fsSL https://clinch.sh/install | shUnnotarized public preview for macOS 14+. The installer authenticates a signed release, verifies its digest, and stages Clinch in Applications. Read the installer source · View on GitHub →
remote controlbeta
clinch-terminal
~/clinch-terminal
✳ claude · opus 5 · falcon-barrel
› hey claude, fix the PR #47 review comments
⏺ Reading PR #47 · 3 review comments
⏺ Editing remote/session.rs · lease.rs
⏺ cargo test · 5,927 passed
✓ Pushed 1 commit to falcon-barrel
- typed on iPhone
- over your tailnet
- run on your Mac
claude · pr-47
tailnet · Elliot's Mac
› what's left on the milestone?
✓ 2 open · both assigned
› rebase onto main
✓ Rebased · 0 conflicts
› hey claude, fix the PR #47 review comments
✓ Pushed 1 commit to falcon-barrel
Send a line from your phone. It runs in the session already open on your Mac.
How it works →$ clinch product tour
Every agent. Every project. One window.
$ clinch features
Built for Claude Code and Codex
I run Claude Code and Codex all day, in a lot of tabs. Every feature below started with something I wanted in my own terminal. Click a feature for a short demo and the commit that introduced it.
Thank you, Warp
I've used Warp as my daily terminal for years, and I love it. When the team announced they were open-sourcing it, I was ecstatic — I could finally tweak the terminal I already lived in and customize it just the way I liked.
Clinch exists only because Warp's team did the hard part — the Rust terminal, renderer, blocks model, and years of polish — then published the client source. None of this would be possible without that work.
In that same spirit, Clinch's source is public too. Most of it is AGPL-3.0, while the warpui crates remain MIT. Take it, fork it, and tune it the way I tuned Warp. And if you want Warp's upstream product and services, go get Warp. It's a fantastic terminal.
— Elliot
What ships in the current release
| Area | Clinch release profile |
|---|---|
| Warp services | No Warp account flow or authenticated Warp service configuration in the stable build. Backend-dependent Warp AI, Drive, teams, and sharing UI are disabled. |
| Telemetry and crashes | No RudderStack destination or write key is configured, and Sentry is not linked. The stable runtime treats telemetry as unavailable: it starts no telemetry timers, writes no queue, and sends no events. |
| Updates | Clinch checks signed release metadata at most once per active day and shows Update available in the header. It downloads nothing until you approve the update; writable installs then quit, swap, and relaunch automatically, while non-writable installs use the authenticated manual path. Builds older than v0.2026.07.20.1643 need one bootstrap install. |
| Platform | macOS 14 or later. The public release is universal for Intel and Apple Silicon. |
| Distribution | Ad-hoc signed with the hardened runtime, but not Developer ID-signed or notarized. Apple has not verified the publisher or artifact. |
Install
macOS 14+ on Intel or Apple Silicon
The current release is a universal technical preview.
Copy this into your terminal to download and install Clinch. The script authenticates an exact signed release before installing the app: it verifies the archive size and SHA-256, bundle ID, version, macOS requirement, universal slices, and structural signature, then stages Clinch in /Applications or ~/Applications.
curl -fsSL https://clinch.sh/install | shWhen it finishes, it opens Clinch — no Gatekeeper approval is needed, because command-line downloads are never quarantined. It does not configure Claude Code or Codex, install plugins, change Gatekeeper settings, or use sudo. Read the current installer source before running it if you prefer. The latest route resolves to a versioned release asset; the script verifies signed metadata and downloads only from that exact tag.
Prefer to verify by hand?
Every versioned release ships Clinch.dmg with a release-key-signed checksum list. The README documents the full manual verification steps, including the Clinch release key. Note that a DMG downloaded in a browser is quarantined and, because the preview is not notarized, macOS will block the first launch until you approve it under System Settings → Privacy & Security → Open Anyway.
Security status
The public build is a technical preview. It is not notarized and has not had an independent security audit.
Public source. The Clinch and upstream client source is public. Most of the project is AGPL-3.0; the warpui and warpui_core crates remain MIT-licensed.
What the installer changes. It authenticates a signed manifest, resolves one exact GitHub tag, verifies the archive size and SHA-256, bundle ID, version, macOS requirement, universal slices, and structural signature, then stages Clinch in /Applications or ~/Applications and opens it. It does not clear quarantine, use sudo, change provider configuration, or install plugins.
What release verification proves. The signed checksum list binds the DMG digest to Clinch's release key. The signed manifest separately binds the exact repository, tag, ZIP identity, size, and digest. GitHub and the project's private release keys are still trusted dependencies.
macOS trust status. The preview is ad-hoc signed, not Developer ID-signed or notarized. Apple does not identify its publisher, and Gatekeeper may require explicit approval.
Audit status. Clinch has automated checks but no independent security audit or broad public beta. Keep another terminal installed and review the source and versioned release before using it for sensitive work.
Privacy and network use
The stable build does not start a Warp account session, analytics or crash reporter. It can make a quiet, at-most-daily GitHub request for signed update metadata. It is not an offline app: features you enable and programs you launch can use the network.
No configured Warp analytics destination. The stable configuration has no RudderStack URL or write key, and Sentry is not linked. Telemetry availability overrides stored upstream defaults; the collector does not schedule, persist, or send telemetry in this channel.
No Warp account or authenticated services. Stable Clinch uses offline placeholders for Warp service configuration and disables backend-dependent UI. The upstream service clients and endpoint constants still exist in the source and binary.
Signed update checks. Clinch may contact GitHub at most once per active day for signed release metadata. Automatic checks do not download the app; download and installation require explicit approval.
Other network use
Programs and integrations. Claude Code contacts Anthropic, Codex contacts OpenAI, and MCP servers, plugins, language servers, remote sessions, and other terminal programs use the network according to their own configuration.
Optional Claude plan gauges. If you enable live Claude plan limits, Clinch asks for access to the Claude Code credential in macOS Keychain and queries Anthropic's usage endpoint.