Configure your proxy and credentials
Connection rules answer where Claude can connect. They are one part of privacy protection; they do not decide which personal files Claude can read or inspect the contents it sends.
Prepare the address and credentials
Section titled “Prepare the address and credentials”Have the host, port and any required username and password ready. Address-format examples without credentials:
| Type | Example |
|---|---|
| SOCKS5 | socks5://203.0.113.10:1080 |
| HTTP | http://203.0.113.10:8080 |
These illustrate the format and are not working endpoints. Keep real passwords out of project files, screenshots and diagnostics you share.
-
When choosing a channel, paste your own proxy address and credentials into CCIso. Confirm the host and port against your own configuration.
-
Click Test connection, then turn on isolation when it passes. The background service is installed during setup (the macOS Installer asks for an administrator password once); configuration is not active evidence until that step completes.
-
Run a Health check and review whether rules are present, forwarding is available, target processes are included and connection tests have completed. Address each finding.
How passwords are stored
Section titled “How passwords are stored”The current macOS core saves proxy secrets in a directory accessible only to the system administrator identity, with files readable and writable only by that identity. It passes forwarding configuration to the engine through a memory pipe. This is not completed Keychain integration or a promise of no plaintext on disk.
These permissions protect the copy stored by CCIso. Copies left in a project configuration or another file need separate handling.
Claude Code and SOCKS5
Section titled “Claude Code and SOCKS5”Anthropic’s network documentation says Claude Code does not directly support SOCKS proxies. CCIso’s local engine connects an HTTP proxy entry point to your configured SOCKS5 exit, without putting a SOCKS5 URL directly in Claude Code proxy variables.
If your proxy already offers an HTTP entry point, see manual configuration for macOS, Windows or Linux. Manual proxy variables do not create private-file isolation.
When a connection fails
Section titled “When a connection fails”Distinguish an offline computer, an incorrect address or credential, inactive system rules and a process outside the boundary. Failure to connect does not by itself establish working protection; a successful connection does not establish that every protection is active either.
Local MCP services, LAN addresses and other network tools may require additional rules. Complete validation notes have not been published; automatic discovery and allowance of every service is not promised.
External configuration references were reviewed on November 1, 2026. CCIso instructions describe macOS version 0.1.7.