The compatibility CLI icc talks to a Unix socket owned by a running imux instance. For security, connections from arbitrary host processes may be denied.
This is intentional isolation, not a broken install.
Prerequisites
- imux running
- icc on PATH from the app bundle
Steps
- 01
Run icc from an imux terminal
Open a terminal surface inside imux and run:
which icc icc --helpPrefer
/Applications/imux.app/Contents/Resources/bin/iccwhen debugging PATH issues. - 02
Do not expect every external shell to attach
A Terminal.app or VS Code integrated terminal may not be allowed to control the live instance. That prevents random scripts from driving focus/automation.
- 03
Use supported automation entrypoints
For automation, start jobs as panes/agents inside imux, or use documented socket policies for your build. Never chmod the socket world-writable.
- 04
Confirm the right instance when using --tag
Debug builds with
--tagisolate sockets and DerivedData. Point tools at the tagged instance; mixing stable and tagged sockets causes confusing denials.
FAQ
Is this the same as membership API keys?
No. Socket control is local desktop automation. Membership API keys are for cloud HTTP.