Using Signeto day to day
Once setup is done, you mostly don't touch Signeto: you ask Claude Code to merge, and your phone asks you. This page covers the rest. Where macOS and Windows differ, each is called out.
What needs sudo
macOS and Linux, after the system install (step 8). Anything that changes the gateway, or reads its private files, needs your admin password. That's the point: an agent doesn't have it.
Without sudo |
With sudo |
|---|---|
signeto status, signeto doctor, signeto system status, and Claude Code itself |
signeto github audit, signeto policy edit, signeto pair --relay, signeto devices, signeto devices revoke, signeto ledger, signeto freeze, secrets |
When a command needs sudo, it says so and prints the full command. It names /usr/local/lib/signeto/bin/signeto (/opt/signeto/bin/signeto on Linux): that's the copy the install checked and root owns, while which signeto comes first on your PATH is up to your account's shell settings, which an agent can change.
Windows. Signeto never needs admin rights on Windows: the gateway runs as your account, so no command needs them. That also means an agent running as you can reach the gateway's files; see What user mode means.
Changing the policy
The policy is signeto.yml. Edit it with signeto policy edit. It shows what changes and asks before it writes. A real change then waits for your phone ("Change this gateway's policy").
- macOS and Linux:
sudo signeto policy editopens the policy in your editor ($EDITOR, elsevi), running as you, not as root. Save and quit. - Windows:
signeto policy editopens the policy in Notepad. Edit it, save, and close the Notepad window: the terminal waits until you do. A change to comments or layout only needs no approval. To use another editor, set$env:EDITORfirst, for example$env:EDITOR = "code --wait".
To decide which actions need approval, and from whom, see Policies.
Upgrading
- macOS: after
sudo npm install -g signetobrings a new version, runsudo signeto system upgradeto move the gateway to it. If you keep Homebrew'snodefirst in your PATH, see Keeping Homebrew's node. - Linux: after
npm install -g signetobrings a new version, runsudo signeto system upgrade. - Windows: after
npm install -g signetobrings a new version, runsigneto stoponce. The next Claude Code tool call starts the new gateway.
Stopping everything at once
In the app, Settings → Emergency stop → Freeze every gateway. Claude Code's requests are refused until you unfreeze.
Logs
- macOS: the gateway writes to
/Library/Logs/Signeto/gateway.log.sudo launchctl print system/dev.signeto.gatewayshows the service.
Checking the record
signeto status # the gateway, the policy in force, and whether it's running
sudo signeto ledger # every request, approval and result, hash-chained
sudo signeto github audit # every commit on main traced back to an approval
sudo signeto ledger export audit.html
On Windows, run the same commands without sudo. Your approvals are also listed on the web: Sign in at the top of signeto.dev, then Ledger (api.signeto.dev/account/ledger), where your browser checks every signature itself.
More
- Passkeys and approvals: signing in, recovery, and why your account can't approve anything.
- Integration guide: what the agent sees while it waits and when you deny.
- Verify a receipt yourself, with no Signeto service involved.
- Troubleshooting and Removing Signeto.