imsg-permissionslisted
Install: claude install-skill soulmachine/skills
# imsg-permissions
imsg (openclaw/imsg, Homebrew) needs three macOS privacy grants; upstream lists them in
[docs/permissions.md](https://github.com/openclaw/imsg/blob/main/docs/permissions.md). How TCC
grants work, and the backup-first steps for a `TCC.db` edit, are in
[macos-tcc.md](~/.agents/docs/macos-tcc.md). Read it before step 3.
The work centres on the **grant table**: one row per parent that runs imsg, one column per gate.
A cell is ✅ only when a real command from that real parent passed.
| Parent | Full Disk Access | Automation → Messages | Contacts |
|---|---|---|---|
| SSH | | | |
| Terminal.app, Ghostty, iTerm2 (each one installed) | | | |
| paseo daemon (charged to its LaunchAgent's first program, `/bin/zsh`, or node on hosts in macbook-provision's `paseo_node_launch_hosts` (mac-mini-m6); with SIP on, node under a zsh job is denied, personal-agent Q284–Q285) | | | |
| imsg as its own process (LaunchAgent) | | | |
| openroutine daemon (charged to `~/.cargo/bin/openroutine`, its LaunchAgent's program; `cargo install` leaves it ad-hoc signed, so each rebuild drops the grant until coding-agent's `devops/openroutine/resign.sh` re-signs it with a self-made certificate, coding-agent Q710; its `tcc-probe` task checks daily) | | | |
## Scripts
- `probe.sh <own-address> [--keep-ssh]` tests all three gates from the parent that runs it, and
sends nothing. `--keep-ssh` only in the SSH row.
- `as-imsg.sh [--tty] <imsg args…>` runs imsg once as its own process (a one-sho