Skip to content
Procket

Install guide

Install the client

Each engineer installs one small program and runs one command. There is nothing to configure per repository and nothing to type: it covers every repository and AI tool on the machine.

What you need

  • macOS 11 or later, Windows 10 or later, or any Linux distribution, on Intel/AMD or ARM.
  • git 2.31 or newer.
  • A GitHub account in an organisation where an owner has installed the Procket GitHub App.

The client is a single signed binary. It runs no background service: git and your AI tool start it for a moment when something happens, and it exits.

1. Install

Pick whichever suits your machine. Package managers keep it up to date for you.

macOS and Linux: Homebrew
brew install procket-dev/tap/procket
macOS and Linux: install script
curl -fsSL https://get.procket.dev/install.sh | sh
Windows: winget
winget install Procket.Procket
Windows: Scoop
scoop bucket add procket https://github.com/procket-dev/scoop-bucket
scoop install procket
Windows: Chocolatey
choco install procket
Windows: install script (PowerShell)
irm https://get.procket.dev/install.ps1 | iex

On Linux, .deb and .rpm packages are attached to every release. For script installs,procket update fetches and verifies the latest version. Procket never updates itself silently.

2. Set up

procket setup

setup prints each change as it makes it:

  1. It sets git's global hooks, so commits, amends, rebases and cherry-picks are recorded in every repository on the machine, including ones you clone later. It adds no pre-commit hook, so it can never block a commit.
  2. It adds a hook to each AI tool it finds: Claude Code, Cursor, Codex CLI or GitHub Copilot.
  3. It opens your browser to sign in with GitHub, and finds every workspace you can record into: your company's, from your GitHub organisation, and your own if you have one. If someone has shared a private repository with you that uses Procket, the page asks whether to record your prompts there, and nothing is recorded until you say yes. Over SSH or in a container, run procket setup --device instead and enter the code it shows in any browser.
  4. It runs procket doctor to check everything is wired up.

Each repository's prompts go to the workspace that owns it: your company's repositories to your company, your own to your personal workspace, a shared repository to its owner's, if you agreed. Anything no workspace covers, such as personal projects or another client's code, is never captured. You can see and change what is recorded on the Recording page in the web app at any time.

3. Check it works

procket doctor

doctor lists what is connected and prints the exact fix for anything that is not. The most common problem is a repository that sets its own core.hooksPath (husky, lefthook or pre-commit), which overrides the global hooks. doctor detects it and shows the lines to add.

Rolling out to a company

Signed MSI (Windows) and pkg (macOS) installers are available for Intune, Jamf, Kandji and similar tools. Push the program; engineers run procket setup and approve once in the browser. Each engineer signs in themselves, because their prompts are attributed to them. An optional policy file can pin the workspace and run setup at first login.

In dev containers and Codespaces, add the Procket dev container feature:ghcr.io/procket-dev/features/procket.

Verifying a download

Every release publishes SHA-256 checksums signed with Sigstore, and a software bill of materials. The install scripts check the checksum before installing anything.