Linux: platform plans and manual setup

The Linux plan brings together Claude connection rules, specific credential checks and findings to support visible, controllable local privacy protection. Results need validation for the distribution and runtime environment.

Preview not released

A Linux version is planned; there is no Linux installer yet (only the macOS version is available). Distribution and kernel requirements, package formats and signing details have not accompanied a release. Planned system services and network rules are not available features.

Platform work still to validate

• Process coverage, startup order and failure behavior for dedicated groups and nftables rules.
• Status display and permission flows across desktop environments.
• Credential storage, checks and recovery.
• Compatibility in environments such as WSL, which cannot be inferred from a standard Linux host.

Later cgroup/eBPF work is a design plan. Process grouping is not a separate system user and does not isolate private folders. A root process can also change system rules and must not be treated as an ordinary user process.

Manual Claude Code configuration available now

This configuration does not need CCIso and does not add file isolation. The examples follow Anthropic’s documentation; they have not been connectivity-tested against your proxy environment here.

If your own HTTP proxy is running on local port 8080:

export HTTPS_PROXY=http://127.0.0.1:8080
claude

Replace the example with your actual address. It affects programs subsequently started from this terminal. Restart an existing session and run /status in Claude Code; the Proxy row should show the address.

For background sessions, merge the setting into ~/.claude/settings.json without overwriting existing configuration:

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

Desktop launchers and systemd user services may have a different environment from this terminal. A shell variable alone does not establish their configuration. A background supervisor may also retain an older environment. Let tasks finish before following Anthropic’s instructions to decide whether to restart it with claude daemon stop --any.

Claude Code does not directly support SOCKS proxies. Keep real passwords out of project configuration committed to a repository.

First check

For manual setup, confirm separately that the setting loaded and the proxy is reachable. Neither establishes complete privacy isolation. A future CCIso Linux release also needs checks of system rules, process coverage and credential permissions. Unknown items are not passed items.

No guessed installation or removal commands are provided here. Use the version-specific instructions on downloads when available.

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