macOS: installation and first checks

The result you need is clear: which Claude connections and credentials are controlled, and which still need attention. Establish the scope before installation and checks.

System requirements

CCIso for macOS is a PKG installer, universal (Apple silicon and Intel), and requires macOS 13 Ventura or later. It is signed with Developer ID and notarized by Apple. The app is free.

Before installing

• Your Claude workflow needs connection rules, specific credential protections and visible checks.
• You have a channel ready: your own SOCKS5 or HTTP address, a tunnel share link (hysteria2 / vless / vmess / trojan / ss), a plain WireGuard (wg-quick) file or a tunnel key file. CCIso does not provide an exit service.
• Installation asks for an administrator password once: the installer places CCIso in the Applications folder and installs a background service.
• Full private-folder isolation and outbound content inspection are not implemented. If either is essential, read the scope first.

Installation and first check

1. Download the installer from downloads and verify its SHA256 as described there. You can also run spctl -a -vv -t install CCIso-0.1.7.pkg in Terminal from your download folder (use the actual filename); the result should include source=Notarized Developer ID.

2. Double-click the installer. The macOS Installer asks for an administrator password once to place CCIso in Applications and install the background service.

3. When installation finishes, CCIso opens by itself. Choose a channel: drag a key file into the window, or paste a share link or your own proxy address.

4. Click Test connection. When it passes, turn on isolation. You still sign in to Claude yourself.

5. Run a Health check and review the findings. If existing Claude processes are outside the boundary, save your work before restarting them as instructed. Check again afterward. An old window still connecting is not evidence of protection.

First-check completion: relevant entry points, rules, processes and connection tests have explicit results. Unknown or unfinished items still need attention. This establishes only the listed checks, not isolation of every personal file.

Activation

The app is free, and basic protection works without activation. To turn on always-on protection, automatic updates and deep clean, open Activate in CCIso, paste the activation code and tap Activate. This computer’s ID is shown in About.

Uninstalling

In CCIso, open Settings → Uninstall. Uninstalling removes isolation, and Claude connects directly again.

Manual proxy configuration without CCIso

These Claude Code examples do not need CCIso and do not add private-file isolation. They follow Anthropic’s documentation; they have not been connectivity-tested against your proxy environment here.

If your own HTTP proxy is listening on local port 8080, run:

export HTTPS_PROXY=http://127.0.0.1:8080
claude

Replace the example port with your own. The variable applies to processes subsequently started from this terminal; restart an existing session. In Claude Code, run /status. The Proxy row should show the configured address. That establishes that the setting was read, not that every connection succeeds.

For background sessions, merge the variable into the env block of ~/.claude/settings.json, preserving existing settings:

{
  "env": {
    "HTTPS_PROXY": "http://127.0.0.1:8080"
  }
}

An editor opened from the Dock is not a process started by this terminal. Do not assume it inherited the new variable. A background supervisor may also retain an earlier environment. Let background tasks finish, then use Anthropic’s instructions to decide whether to run claude daemon stop --any and restart the supervisor.

Keep real proxy passwords out of committed project settings. Check for lowercase proxy variables or managed settings that may override your change.

Common problems

• Invalid address: include the correct HTTP or HTTPS scheme; do not put a SOCKS5 URL directly into Claude Code.
• Terminal works but editor does not: compare the configuration and environment each process actually reads.
• Connection works but privacy scope is unclear: read how it works. Connectivity does not establish file permissions.

Continue with your own proxy and troubleshooting. Source: Anthropic’s network documentation, reviewed on November 1, 2026.