How it works

A small program, a web app, and one connection.

Patchkin has three parts: a program on each machine, the Patchkin service that connects everything, and the web app you use. This is the whole picture, live.

  • Machines connect out. Nothing connects in
  • Your browser and phone talk to Patchkin
  • Your pipeline asks Patchkin one question
What crosses the line

Four lanes between your machine and Patchkin.

What goes each way, and what never does.

Your machineClaude Code, Codex, Cursor CLI, OpenCode, Aider, Gemini CLI
PatchkinThe web app, your rules and the records
Terminal viewmachine to Patchkin
What the agent prints, streamed to your browser over TLS. With end-to-end encryption on, Patchkin cannot read it.
Small eventsmachine to Patchkin
A session started, a commit finished, a check passed. Names, counts and results only.
Your instructionsPatchkin to machine
Launch this agent, send this input, apply this standard, use this policy.
Never crossesstays on your machine
File contents, what people type, secret values, the output of your tests.
Getting started

From nothing to a running agent.

Create your organization

Sign in to the web app and create an organization and a team. Invite people, or connect single sign-on.

Pair a machine

In Machines, choose Pair machine. The app gives you a one-time code and the command to run on the machine. The program connects out and appears in your list.

Launch an agent

Choose the machine, the tool and a folder, and start. Open the live terminal to watch or take over.

Add standards

Write a rule once in Team standards. It reaches each tool on each paired machine within moments.

Turn on governance

Switch it on in observe mode. Look at sessions, findings and cost. When you are ready, connect your git host and make the merge check required.

The Machines page with three paired machines online.

The program on your machine does

  • Open one encrypted connection out to Patchkin
  • Start agents and terminals when you ask
  • Apply your standards in each tool’s own files, inside a marked block
  • Install git hooks, only when governance is on
  • Report small events: a session started, a commit finished, a check passed
  • Update itself when you click Update in the web app

It does not

  • Accept inbound connections
  • Read or upload your files or prompts
  • Overwrite your own rules files
  • Run governance hooks when governance is off
Requirements

Short list.

Machines

macOS (Apple Silicon or Intel), Linux or Windows, with outbound HTTPS. An HTTP proxy is fine.

Agents

Whichever tools you already use, installed the way you normally install them.

Git host and pipeline

Optional, for the review rule and the required check. GitHub, GitLab, Bitbucket, Azure DevOps and Jenkins are supported.

Ready to pair your first machine?

It takes about five minutes.