Skip to content

Tags

Tags

v1.9.2

Toggle v1.9.2's commit message
1.9.2: agents are told to ask once for a grant; "not approved" and "n…

…o secret named" say what really happened

- To an AI agent only (--intent, and a known agent or CLAUDECODE/AI_AGENT set), one line on stderr: after an
  approved run prompt, a tip to ask once for a timed grant; from the same app's second prompt in 30 minutes, how
  many and for which keys (counted from the access log, nothing new stored); after a prompt nobody approved, that
  the person may be away and not to retry in a loop.
- "touchenv: not approved" says why when known: declined, the Mac locked, another prompt took over, closed before
  anyone answered, or touchenv stopped (a time limit, Ctrl-C) while the prompt was open (now logged too).
- "no secret named X" only for a secret that is really missing. With the Mac locked, iCloud Keychain's listing
  fails (errSecInteractionNotAllowed) and came back empty, so a synced secret that exists was reported missing.
  Now: "couldn't check whether X is stored: the Mac is locked ...". Same for ls --synced, which printed nothing.
  Keychain read errors are put in words (cancelled, auth failed, interaction not allowed).
- tests/hints-tests.swift; README and docs/grants.md: "For AI agents: ask once".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WX9XbCBeBdBFHDAV1YvXmG

v1.9.1

Toggle v1.9.1's commit message
1.9.1

touchenv ls --synced (see the commit before this one); nothing else changed.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WX9XbCMWGB7qhVi5AgTb9i

v1.9.0

Toggle v1.9.0's commit message
README: approving from afar, with a grant or a code; help ends with w…

…here the instructions are

- README "Approving from afar": a grant made before leaving, a code from
  the phone when it has run out, and how the two differ.
- touchenv's help (both builds) ends with a line pointing at
  https://github.com/ptrinh/touch-env for full instructions and updates.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WX9XbCMWGB7qhVi5AgTb9i

v1.8.3

Toggle v1.8.3's commit message
1.8.3: the prompt shows what really runs; threat model and security p…

…olicy

- Who asks is named by its executable, not by the argv[0] it chose: a program
  started as "claude" no longer passes for Claude Code (it shows as
  "<file> (calling itself claude)").
- run's prompt says which file runs (as found on PATH), warns of environment
  variables that make it run other code (NODE_OPTIONS, PYTHONPATH, BASH_ENV,
  DYLD_INSERT_LIBRARIES…), and of --no-mask; the --password summary too.
- docs/threat-model.md; SECURITY.md (private reporting, US$100 bounty);
  security.md, README and windows.md no longer overstate what malware running
  as you can't do; release.sh's note on the Windows zips is current.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q1tC8pHZuLCqDE9MGuX4ai

v1.8.2

Toggle v1.8.2's commit message
1.8.2: sync says what a synced key gives up

touchenv sync and set --sync now say, each time a key starts syncing,
that a synced key is guarded by touchenv's own code rather than macOS's
Touch ID lock, and that production keys belong on this Mac only. Help
says it too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q1tC8pHZuLCqDE9MGuX4ai

v1.8.1

Toggle v1.8.1's commit message
1.8.1: touchenv get ends the line when it prints to a terminal

zsh marked the value's end with a highlighted % because no line break
followed it. A terminal now gets one; a pipe or $(...) still gets the
value alone. macOS and Windows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q1tC8pHZuLCqDE9MGuX4ai

v1.8.0

Toggle v1.8.0's commit message
1.8.0: touchenv run hides the secrets' values in output an AI assista…

…nt or a program reads

When an AI assistant runs touchenv run, or the output goes to a pipe or a
file rather than a terminal, the command's stdout and stderr have the
secrets' exact values (and each long line of a multi-line one) replaced
with ***REDACTED***, also when split across writes. A person's own
terminal gets the output as it is; --no-mask turns it off. macOS and
Windows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q1tC8pHZuLCqDE9MGuX4ai

v1.7.6

Toggle v1.7.6's commit message
1.7.6: the copyright line under the title in help

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q1tC8ri8LWyhP4CB8qimFJ

v1.7.5

Toggle v1.7.5's commit message
1.7.5: touchenv sync / unsync NAME ... move saved secrets to or from …

…iCloud Keychain

Until now moving a secret between this Mac only and iCloud Keychain meant reading it out and saving it
again through a shell (touchenv run NAME:file -- sh -c 'touchenv set --sync NAME < "$NAME"'), and a
mistake in that shell could print the value. sync and unsync do it inside touchenv: one Touch ID for
every name, the value read and stored again without leaving the process, the new item added before the
old one is deleted (replaceSecret), an SSH key's attributes kept, names already in place skipped, a
mistyped name refused before any prompt, one access-log line. unsync says the secret leaves your other
Macs. Windows: refused (keys stay on the PC).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q1tC8ri8LWyhP4CB8qimFJ

v1.7.4

Toggle v1.7.4's commit message
1.7.4: the keyboard goes back to the app you were in after the prompt

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q1tC8ri8LWyhP4CB8qimFJ