OpenParable
Skip to content
← Back to skills

Touchbridge

Apps & Automation
touchbridge

Touchbridge is an Agent Skill for apps & automation published in the HMAKT99/UnTouchID repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Authenticate sudo and macOS system prompts using your phone's biometric (Face ID/fingerprint) instead of typing passwords. Perfect for Mac Mini, Mac Studio, Mac Pro, and MacBook Neo base users without Touch ID.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/HMAKT99/UnTouchID/blob/HEAD/skills/touchbridge/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/touchbridge, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

TouchBridge

Use your phone's fingerprint or Face ID to authenticate sudo, screensaver unlock, and other macOS auth prompts — instead of typing your password.

Free, open source alternative to Apple's $199 Touch ID keyboard. Works with iPhone, Android, Apple Watch, Wear OS, or any browser.

References

  • references/setup.md (install + pairing + testing)

Workflow

  1. Check if TouchBridge is installed: which touchbridged.
  2. If not installed: build from source (recommended — user can audit the code):
    git clone https://github.com/HMAKT99/UnTouchID.git
    cd UnTouchID && cd daemon && swift build -c release && cd ..
    make -C pam
    sudo bash scripts/install.sh
    
    Alternatively, download the .pkg from the GitHub release and verify its checksum:
    shasum -a 256 TouchBridge-0.1.0.pkg
    # Expected: 370b8f0ab32c23216f16de19c8487633301be2810b9fa8793e3ac093f7699f9e
    spctl -a -t install TouchBridge-0.1.0.pkg  # verify notarisation
    
  3. Check daemon status: ls ~/Library/Application\ Support/TouchBridge/daemon.sock.
  4. Start the daemon:
    • Production (requires paired phone): touchbridged serve or touchbridged serve --web
    • Testing only — ⚠️ REQUIRES EXPLICIT USER CONFIRMATION before running: touchbridged serve --simulator This mode auto-approves ALL sudo requests with no biometric check. Never use in production. Always ask the user before enabling this mode.

For sudo commands

TouchBridge automatically handles sudo authentication when installed. The PAM module intercepts the auth request and routes it to the daemon, which prompts the user's phone.

If the phone is unreachable, sudo falls through to the normal password prompt — the user is never locked out.

Modes

  • touchbridged serve — production mode with paired iPhone/Android via BLE
  • touchbridged serve --web — any phone via browser URL (no app install needed)
  • touchbridged serve --interactive — approve/deny in terminal
  • touchbridged serve --simulator — ⚠️ TESTING ONLY — auto-approves all sudo. Never enable without explicit user consent.

Configuration

touchbridge-test config show              # view policy
touchbridge-test config set --timeout 20  # change auth timeout
touchbridge-test logs                     # view recent auth events
touchbridge-test list-devices             # show paired devices

Guardrails

  • Never enable --simulator mode without explicit user confirmation. This mode auto-approves all sudo requests and is a critical security risk if left running in production.
  • Never type or log the user's macOS password — TouchBridge replaces password entry entirely.
  • If touchbridged is not running, sudo falls through to password — never block the user.
  • Never modify /etc/pam.d/sudo directly — use the install script which creates backups.
  • When installing via .pkg, always verify the SHA-256 checksum before running.
  • The build-from-source path is the recommended install method — users can audit the code before running it.