Install on Windows (self-hosted)

This page takes a Windows 11 PC from nothing to Claude Code asking your phone before it merges a pull request into main: what to install first, what each step of setup prints and what you do, and your first approved merge. How setup works explains what each step does and why. Allow about fifteen minutes, most of it installing tools.

Self-hosted means the gateway, the part that holds your GitHub App's key and checks your phone's signature, runs on this PC, under your own account (Windows has no system install yet; see the note below). Signeto never holds your credentials. This is the free plan.

This guide on video, in under 7 minutes: install, setup steps 1 to 7 in PowerShell, the first merge approved on the phone, and the record on the web. The phone is an iPhone; Android works the same. The video is served from signeto.dev; nothing loads from other sites. The signeto CLI you install may be newer than the one recorded, so a few steps may be worded differently; the steps on this page are kept current. Prefer YouTube? Watch it there.

On Windows, the gateway runs as your account. On a Mac or Linux machine, the last step of setup moves the gateway to its own system account, out of an agent's reach. Windows doesn't have that step yet. Signeto still stops Claude Code from merging into main with your GitHub login, and every merge it makes through Signeto waits for your phone. But an agent that can run any command it likes as you can read the gateway's files, including the GitHub App's key, and use them to merge without asking. See What user mode means before you rely on it.

Before you start

You need:

Everything below runs in PowerShell (Windows Terminal opens it by default). Use your normal account, not "Run as administrator": Signeto never needs admin rights on Windows.

Check what you already have

Paste this into PowerShell to see what's installed already, and skip the steps that are done:

git --version; node --version; where.exe node; gh auth status; Get-ExecutionPolicy; claude --version; signeto --version

The term '…' is not recognized means that tool isn't installed yet, or was installed after this PowerShell window opened: open a new window and paste it again. Otherwise:

1. Install Git, Node.js and the GitHub CLI

winget install -e --id Git.Git
winget install -e --id OpenJS.NodeJS.LTS
winget install -e --id GitHub.cli

Signeto needs Node.js 22.13 or newer; the LTS package is newer than that. You can also use the Windows installer from nodejs.org instead of winget.

Close PowerShell and open a new window, so it picks up the new programs, then check:

node --version
git --version
gh --version

2. Let PowerShell run npm

A fresh Windows install refuses to run PowerShell scripts, and npm is one. Allow scripts for your account (local scripts, and downloaded ones that are signed):

Set-ExecutionPolicy -Scope CurrentUser RemoteSigned

Without this, every npm command fails with "npm.ps1 cannot be loaded because running scripts is disabled on this system".

3. Tell Git who you are, and sign in to GitHub

git config --global user.name "Your Name"
git config --global user.email "you@users.noreply.github.com"
gh auth login

Use the email you want on your commits; GitHub's noreply address (Settings → Emails) keeps your own private. gh auth login signs the GitHub CLI in as you: setup uses it once, to protect your branch.

4. Install Claude Code

irm https://claude.ai/install.ps1 | iex

Then open a new PowerShell window and run claude once to sign in. If PowerShell says "The term 'claude' is not recognized", the installer's folder isn't on your PATH yet. Add it for your account, then open a new window:

[Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path", "User") + ";$env:USERPROFILE\.local\bin", "User")

5. Install Signeto

npm install -g signeto
signeto --version

Run setup

Open PowerShell in your repository's folder and run setup:

cd ~\Documents\your-repo
signeto setup

Setup reads the repository name from the origin remote; pass --repo OWNER/NAME if that's not right. It runs seven steps. Each first checks whether it's already done, so if one fails, fix what it says and run signeto setup again: it picks up where it stopped.

Step What happens
1. Gateway Creates this machine's gateway in %USERPROFILE%\.signeto: its key, a starter policy, the ledger and an encrypted store for secrets
2. Account Signs you in to Signeto with your passkey and registers the gateway
3. Phone Pairs your phone by scanning a QR code
4. GitHub Creates a GitHub App for this gateway and protects your default branch
5. Claude Code Adds Signeto to Claude Code for this project
6. Test Sends a harmless request to your phone
7. Doctor Checks the whole chain

Setup starts with a header, then numbers each step as it goes:

Signeto setup
  home C:\Users\you\.signeto · project C:\Users\you\Documents\your-repo · repo you/your-repo · user mode
  Each step checks what is already done. Stop any time; run signeto setup again to continue.

1/7 Create this machine's gateway

A line starting with ? is a question: type an answer, or press Enter to take the default shown in [brackets]. A step that's already done prints ✓ already done and setup moves on. The sections below show what each step prints and what you do; each links to How setup works for what the step is for.

Step 1: Gateway

Setup asks for two names:

1/7 Create this machine's gateway
? Name for this gateway [your-pc]:
? Your approver name (used in the policy) [you]:

What to do:

  1. Name for this gateway. Press Enter for the default (your PC's name), or type one: letters, digits, dots, dashes and underscores, no spaces. It appears on your phone as "Request from name".
  2. Your approver name. Press Enter for the default (your login name), or type one: 2 to 32 lowercase letters, digits, _ or -, starting with a letter. It goes into the policy as the person who approves. Pick it once and keep it.

Setup then creates the gateway in %USERPROFILE%\.signeto and prints four lines:

  ✓ 1/4  Gateway key        created  Ed25519  C:\Users\you\.signeto\gateway-key.json (0600)
  ✓ 2/4  Policy             wrote C:\Users\you\.signeto\signeto.yml
  ✓ 3/4  Credential store   created  ...
           ⚠ anything running as you, an agent with a shell too, can read it; ...
  ○ 4/4  Approver           none yet: pair your phone (below). Until then every action that needs approval fails closed.

✓ Gateway your-pc is ready.

"Approver none yet" is expected: your phone becomes the approver in step 3. The ⚠ under the credential store is about the key that unlocks the secrets store: on Windows it's a file in %USERPROFILE%\.signeto, which anything running as you can read. See What user mode means. What this step sets up: 1. Gateway.

Step 2: Account

Setup prints a sign-in link and a short code, then waits:

2/7 Sign in to your Signeto account
Sign in to the relay to register this gateway:
  1. open   https://api.signeto.dev/...
  2. check  the page shows CODE and approve it with your passkey

What to do:

  1. Open the link in your browser. Setup doesn't open the browser itself.
  2. No account yet? Create one on that page.
  3. Check the page shows the same code as the terminal. If it doesn't, close the page and don't approve.
  4. Approve with your passkey. Windows can keep a passkey with Windows Hello (face, fingerprint or PIN). If your passkey is on your phone, choose Use a phone or tablet in the browser's prompt and scan the QR code with your phone's camera; Bluetooth has to be on for both.
  5. Go back to PowerShell. It continues by itself:
    ✓ gateway your-pc registered at https://api.signeto.dev
    

If the code expires before you approve, run signeto setup again for a new one. Which passkeys work, signing in on a VM, and recovery: Passkeys and approvals. What your account is for: 2. Account.

Step 3: Phone

Setup asks for a name for your phone, then shows a QR code:

3/7 Pair your phone
  Install the Signeto app and sign in, then tap Pair and scan the QR code shown below.
? Name for your phone (used in the policy) [phone]:

What to do:

  1. Type a name for the phone (for example iphone or pixel), or press Enter for phone. It's used in the policy's device list.
  2. On the phone, open the Signeto app and sign in with the same account as step 2.
  3. Tap Pair and scan the QR code in the terminal. If the QR code doesn't fit in the window, make the window bigger or the font smaller (Ctrl and −) and scan again.
  4. The terminal shows the device that scanned it and asks you to confirm:

    Device claiming this pairing
      fingerprint ...
      name        Your iPhone
      platform    ios
      attestation verified (App Attest)
      Check the fingerprint against the phone (Gateways tab › This iPhone, or This phone on Android) before you accept.
    ? Pin this device for approver you? [y/N]
    

    On an Android phone, name is its model (for example Pixel 8), platform is android and attestation is verified (Android Key Attestation).

  5. In the app, open the Gateways tab and compare the fingerprint under This iPhone (This phone on Android) with the one in the terminal. If they match, type y and press Enter. If they don't, press Enter (the answer is no) and start the step again.

Setup ends the step with ✓ paired Your iPhone through the relay and adds the phone to your approver's devices in the policy. If the app can't sign in, see Passkey sign-in on the phone. What pairing changes: 3. Phone.

Step 4: GitHub

This step has three parts, and setup numbers them 1/3 to 3/3: create a GitHub App, install it, protect the branch.

What to do:

  1. Create the App. Your browser opens GitHub with the App's form already filled in (if nothing opens, open the link the terminal prints). Click Create GitHub App. GitHub may ask for your password first.
  2. Install it. GitHub then asks where to install the App. Choose Only select repositories, pick your repository, and click Install. The terminal waits until it sees the install.
  3. Protect the branch. Back in PowerShell, setup asks:

    Create ruleset "main only via Signeto" on you/your-repo with your gh login (you)? [y/N]
    

    Type y and press Enter. Pressing Enter alone answers no, and setup prints the ruleset to add by hand in GitHub's settings.

When it's done:

  ✓ 1/3  GitHub App   created YOUR-APP (id 1234567) · https://github.com/apps/...
  ✓ 2/3  Install      installed · covers you/your-repo
  ✓ 3/3  Protect      ...

✓ GitHub is set up for YOUR-APP.

From now on, only the App can update main: gh pr merge, git push and the Merge button on GitHub no longer work for main, for anyone, including you and the agent. That is what makes the approval required. See Why the branch has to be protected. If the ruleset step warns about a private repository, see Private repositories on GitHub Free.

Step 5: Claude Code

Nothing to do in this step: setup asks no questions. It adds the gateway to Claude Code for this project only, and allow rules for the two Signeto tools in .claude\settings.local.json (why: 5. Claude Code). Look for these two lines:

✓ added MCP server signeto (local scope) for C:\Users\you\Documents\your-repo
✓ claude mcp get signeto: √ Connected

If it says the claude command was not found, install Claude Code (step 4 of "Before you start"), open a new PowerShell window and run signeto setup again.

Step 6: Test

Setup offers to send a harmless request to your phone:

6/7 Send a test request to your phone
? Send a harmless test request to your phone now? [Y/n]

What to do:

  1. Press Enter (the default is yes). The terminal shows a six-character code and waits up to two minutes:

    Sending a test request to Your iPhone through https://api.signeto.dev
    
      Code: K7M2QX
    
      On your phone: open the notification, check the code matches, and approve.
    
  2. On the phone, open the Signeto notification.

  3. Check the code on the phone matches the terminal, then approve.

Nothing runs when you approve; the terminal confirms the round trip:

✓ approved on Your iPhone by you

If nothing arrives, open the app: the request shows there too. If it says no answer, check notifications are allowed for Signeto and the app is signed in, then run signeto test. More: 6. Test.

Step 7: Doctor

Nothing to do but read. signeto doctor checks the whole chain and prints a fix next to anything wrong. On Windows, expect one warning, and only this one:

Privilege boundary
  ⚠ user mode: the gateway runs as your account
    Agents with a shell on this account can bypass approvals. Windows has no system install yet, so the gateway runs as your account. Keep agents you do not trust off this account.

Under Bypass risks, doctor lists your own GitHub credentials on this machine (the gh login, Git Credential Manager) and should say the ruleset refuses them:

Bypass risks
  ✓ your own GitHub credentials cannot reach the protected branches
    gh logged in as you · git credential helper manager; the ruleset refuses them on OWNER/NAME

Setup then finishes with:

✓ Signeto is set up. Restart Claude Code in C:\Users\you\Documents\your-repo and ask it to merge a PR: your phone will ask you first.
  To remove it all again later: signeto teardown (the same steps in reverse).

⚠ Agents with a shell on this account can bypass approvals. Windows has no system install yet, so the gateway runs as your account.

If doctor shows any other ⚠ or ✗, do what the line under it says and run signeto doctor again. What doctor checks: 7. Doctor.

There is no step 8 on Windows: sudo signeto system install is for macOS and Linux.

If a step fails

Setup stops and says where:

✗ stopped at "github" (exit 1). Fix what it says above, then run signeto setup again; finished steps are skipped.

Read the lines above it, fix what they name, and run signeto setup again from the same folder. To leave a step out, pass --skip with its name: gateway, account, phone, github, claude, test or doctor. Errors by name: Troubleshooting.

What user mode means

On a Mac or Linux machine, sudo signeto system install moves the gateway to its own system account. Your account, and so an agent running as you, then can't read its keys, edit its files or replace its code. Windows doesn't have that yet, so the gateway runs as you.

What Signeto does on Windows:

What it can't do yet: an agent that runs arbitrary commands as you can read everything in %USERPROFILE%\.signeto, including the encrypted store's key and so the GitHub App's private key. With that key, it could merge without asking your phone, or replace the signeto program.

Until Windows has a system install:

Your first approved merge

Restart Claude Code in the repository's folder and type /mcp: signeto should show as connected. Open a pull request (or ask Claude Code to make one), then ask Claude Code to merge it.

Claude Code may try gh pr merge first. GitHub refuses it, because of the ruleset, and Claude Code then uses Signeto's merge tool. Your phone shows the request: the repository, the pull request, the target branch, the merge method and the exact commit. Approve it, and the merge goes through with a green Signeto check on the commit. Deny it, and Claude Code is told you said no, with your reason if you gave one.

Then look at the record:

signeto status
signeto ledger
signeto github audit

signeto status shows the gateway, the policy in force and whether it's running:

  gateway    ✓ running (pid 4780) · 1 MCP session · 0 pending approval(s) · \\.\pipe\signeto-45525a766918857e
  mode       ⚠ user mode. Agents with a shell on this account can bypass approvals. Windows has no system install yet, so the gateway runs as your account.

The gateway runs in the background: the first Claude Code session that needs it starts it, every session for the same home shares it, and it stops by itself a few minutes after the last one closes. Claude Code reaches it through a named pipe, \\.\pipe\signeto-…, rather than a file.

Next