Skip to content

Releases

touchenv 1.9.2

Choose a tag to compare

@ptrinh ptrinh released this 18 Nov 18:10

For AI agents: ask once. An agent that asks for Touch ID now and then over a long task (notarize, then a store upload, then signing) gets prompts nobody may be there to answer. touchenv now nudges it, on stderr, one line at a time, only when an agent asks (--intent, and a known agent or CLAUDECODE / AI_AGENT set); your own terminal sees none of it:

  • after an approved run prompt: a tip to ask once now with touchenv grant --intent "<why>" --for 2h --uses 20 KEY …
  • from the same app's second prompt in 30 minutes: how many prompts and for which keys, and one touchenv grant for the rest (counted from the access log; nothing new is stored)
  • after a prompt nobody approved: the person may be away; don't retry in a loop, finish what needs no secret and ask once

Clearer errors.

  • touchenv: not approved says why when touchenv knows: declined, the Mac locked while the prompt was open, another Touch ID prompt took over, closed before anyone answered, or touchenv stopped (a tool's time limit, Ctrl-C) while the prompt was open.
  • Fixed: with the Mac locked, run, get, grant and rm said no secret named X for an iCloud-synced secret that exists (the Keychain can't list synced items while the Mac is locked, and an empty list was taken as "none"). Now: couldn't check whether X is stored: the Mac is locked, and the Keychain can't be read until it is unlocked. ls --synced says so too instead of printing nothing.

See For AI agents: ask once.

macOS only. Windows is unchanged: use the Windows zips of 1.9.1.

touchenv 1.9.1

Choose a tag to compare

@ptrinh ptrinh released this 16 Nov 11:06

touchenv ls --synced (Mac) prints the names of the secrets synced through iCloud, without Touch ID. macOS doesn't guard those names, and touchenv already says whether a name is synced when it refuses --password or --totp. It is there so a tool such as bordercheck (v0.5.20) can tell you which keys rest on touchenv's own check rather than the Touch ID lock. Never a value; touchenv ls, which also names the secrets kept on this Mac only, still asks.

Nothing else changed since 1.9.0 (grants from afar with a code from your phone: see Approving from afar).

macOS and Windows (beta); the Windows exe is signed (SENPRINTS LLC).

touchenv 1.9.0

Choose a tag to compare

@ptrinh ptrinh released this 16 Nov 10:57

Approving a grant from afar, with a code from your phone. Away from the machine and driving an agent from your phone, you can now approve a timed grant with a six-digit code from an authenticator app, instead of Touch ID or Windows Hello:

touchenv totp setup --max-for 8h --max-uses 20     # once, at the machine, yourself
touchenv grant --intent "deploy" --totp 123456 --for 8h --uses 20 DEPLOY_KEY     # from afar: the agent runs this
  • Mac: for secrets synced through iCloud only (as --password): a secret kept on this Mac only stays behind Touch ID. Setup shows the key as a QR code in touchenv's own window, never in the terminal.
  • Windows (beta): for the keys you choose with touchenv totp allow NAME …. The touchenv service keeps the key behind the codes and a copy of each allowed key, encrypted to its own account, and checks every code itself; run touchenv service install again with this build. Setup shows the key as text to type into the app. Not yet tried on a real PC: it has passed the automated tests on Windows only.
  • A code works once, within the limits chosen at setup (12 hours and 100 uses unless you choose less). Wrong codes delay the next try; the fifth in a row locks codes until touchenv totp unlock at the machine. An AI assistant can't run totp setup.
  • A code doesn't say what it approves: the agent you give it to chooses the keys and the limits, within those of setup. Set the limits low and keep signing keys and admin tokens out of its reach. The README's new section Approving from afar compares it with a grant made before you leave; docs/security.md and docs/windows.md say what it gives up.

touchenv with no arguments, and touchenv help, now end with where the full instructions and updates are.

macOS and Windows (beta); the Windows exe is signed (SENPRINTS LLC).

touchenv 1.8.3

Choose a tag to compare

@ptrinh ptrinh released this 14 Nov 22:11

The Touch ID prompt shows more of what you approve.

  • Who asks is named by the program's executable, not by the name it gave itself: a program started as claude no longer shows as Claude Code (with Claude's icon); it shows as <its file> (calling itself claude).
  • run says which file the command runs, as found on your PATH, so a program placed earlier on PATH can't pass for the one you know.
  • run warns, on a line that is never folded away, of environment variables that make a command run other code (NODE_OPTIONS, PYTHONPATH, BASH_ENV, DYLD_INSERT_LIBRARIES and others), and of --no-mask.

Security policy and threat model. SECURITY.md: report vulnerabilities privately (Security → Report a vulnerability); a confirmed one in scope earns US$100. docs/threat-model.md says what each kind of attacker can and can't do, and what is worth an independent review. docs/security.md, the README and docs/windows.md no longer overstate what malware running as you can't do once you approve a request or a grant is on.

macOS and Windows (beta); the Windows exe is signed (SENPRINTS LLC).

touchenv 1.8.2

Choose a tag to compare

@ptrinh ptrinh released this 14 Nov 18:15

touchenv sync and touchenv set --sync now say, each time a key starts syncing, what a synced key gives up: it is guarded by touchenv's own code rather than macOS's Touch ID lock, so on any of your Macs, malware with admin rights that turns off System Integrity Protection can read it without your finger. Keep production keys (SSH, signing, deployment, payments) on this Mac only (touchenv unsync NAME). Help says it too.

Nothing else changed since 1.8.1. macOS and Windows (beta); the Windows exe is signed (SENPRINTS LLC).

touchenv 1.8.1

Choose a tag to compare

@ptrinh ptrinh released this 14 Nov 06:31

touchenv get now ends the line when it prints to a terminal, so the prompt starts on a line of its own (zsh no longer marks the end of the value with a highlighted %). A pipe or $(…) still gets the value alone, exactly as stored.

Nothing else changed since 1.8.0. macOS and Windows (beta); the Windows exe is signed (SENPRINTS LLC).

touchenv 1.8.0

Choose a tag to compare

@ptrinh ptrinh released this 14 Nov 05:43

touchenv run now hides the secrets' values in what the command prints, when an AI assistant runs it or the output goes to a program (a pipe, a file) rather than a terminal. A command that echoes a key (env, curl -v, an error message) then shows ***REDACTED*** in its place, so the key does not end up in the assistant's context or its chat history:

$ touchenv run --intent "deploy" GH_TOKEN -- ./deploy.sh | cat
deploying with ***REDACTED***
  • Each secret's exact value is replaced, also when the command writes it in pieces, and each long line of a multi-line one (a PEM key). Values shorter than 6 characters are left alone.
  • Your own terminal gets the output as it is. Assistants are recognised as for --intent (Claude Code, Codex, Cursor's agent, Gemini CLI, aider, Goose, opencode), and by CLAUDECODE / AI_AGENT.
  • --no-mask turns it off for a run.

macOS and Windows (beta). The Windows exe is signed (SENPRINTS LLC).

touchenv 1.7.6

Choose a tag to compare

@ptrinh ptrinh released this 14 Nov 03:11

Help now starts with the copyright line under the title, on macOS and Windows (beta):

touchenv 1.7.6 — secrets in the macOS Keychain, every read behind Touch ID
© Phil Trinh - SENPRINTS 2026

Nothing else changed since 1.7.5. The Windows exe is signed (SENPRINTS LLC).

touchenv 1.7.5

Choose a tag to compare

@ptrinh ptrinh released this 14 Nov 03:05

macOS: touchenv sync NAME … and touchenv unsync NAME … move saved secrets into or out of iCloud Keychain. One Touch ID covers every name, and the value never leaves touchenv: no shell, file or pipe in between. The new copy is stored before the old one is deleted, SSH keys keep their attributes, names already in place are skipped, and unsync says the secret leaves your other Macs.

Windows (beta): sync and unsync say keys stay on the PC. Nothing else changed since 1.7.4; the exe is signed (SENPRINTS LLC).

touchenv 1.7.4

Choose a tag to compare

@ptrinh ptrinh released this 12 Nov 13:48

macOS: after you touch (or cancel), the keyboard goes back to the app you were in. Before, touchenv run left it with touchenv, which has no window, while the command ran, and macOS then picked some other app.

Windows: nothing changed since 1.7.3; the exe is signed (SENPRINTS LLC).