~/.claude-science/config.toml on macOS and Linux. Every key has a default, so the app starts with no file present; administrators deploy the file with device management to set fleet policy. The file is read once at startup, so changes take effect after a restart. The claude-science command accepts --config <file> to read a different file for one run.
Network configuration
The network-related keys, grouped by the TOML table each belongs to. For the package-mirror keys ([conda] channel_mirror, pip_index_url, and ca_bundle) and the proxy key ([network] proxy), a value set in the file takes precedence over the matching Settings control, which then shows as managed by your organization so a member cannot override it. The [sandbox.network] lists are additive instead: they add to the member-managed lists under Settings > Network and lock nothing. The [network] ca_bundle, no_proxy, and mcp_x509_strict keys and [conda] allow_insecure_mirror have no in-app control.
App connection keys
The[network] table configures the app’s own connections to Anthropic.
Package download keys
The[conda] table configures where analysis environments fetch packages from and how those downloads verify certificates.
Sandbox network keys
The[sandbox.network] table adjusts the network allowlist the analysis sandbox enforces. Members see the same allowlist under Settings > Network.
Related resources
- Use Claude Science on a corporate network: how to apply these keys for a proxy, TLS inspection, or an internal mirror
- Network requirements: the built-in allowlist and denylist these keys adjust
- Manage Claude Science on devices: deploying
config.tomlwith device management - Command line settings: the
--configand--data-dirflags