Skip to content

Configuration variables ​

This page lists the Phillip environment variables on your machine. The server-side variables of Tara, Ryoma, and Bandum, for people who run their own install, are on the developer site. Phillip doesn't save tokens in configuration files. It keeps them in the operating system's secret store.

Precedence ​

Phillip takes a value from the earlier source and falls back to the next if it's missing. The order is environment variables, then the project's phillip.lock and .claude/settings.json, then the user's config.json in Phillip's data directory, and finally the built-in defaults.

The default data directory is ~/.config/phillip on Linux and macOS (following XDG_CONFIG_HOME if you set it) and %APPDATA%\phillip on Windows. To change it, set PHILLIP_HOME.

Tara and sign-in ​

VariableDescription
PHILLIP_TARA_URLTara address, for example https://tara.phillipcli.cloud. ph tara login --url or the install script saves this value
PHILLIP_TARA_TOKENTara personal token, for CI or machines without a secret store. Overrides the saved token
PHILLIP_TARA_KEYSTrusted public keys ed25519:<base64>, separated by commas. Overrides the list in the configuration. If empty, only sha256 is checked
PHILLIP_TARA_COMMUNITYSet deny to forbid installing community resources (not yet reviewed), even with --yes. This ban applies to add, install, and upgrade
PHILLIP_ORGSlug of the organization to use, for CI. It overrides the organization saved by ph login or ph org switch without changing it, and Phillip then uses the token saved for that organization. Example: acme
PHILLIP_HOMEPhillip's data directory: configuration, package cache, local lock

Ryoma and Bandum ​

VariableDescription
PHILLIP_DOCS_URLAddress of the documentation site that ph docs opens. Default https://phillipcli.cloud
PHILLIP_RYOMA_URLAddress of Ryoma, which receives telemetry. By default taken from the configuration or the install script
PHILLIP_BANDUM_URLAddress of the local Bandum web UI, default http://localhost:8070
PHILLIP_BANDUM_BINAbsolute path to a prebuilt Bandum binary. When you set this, Phillip doesn't download Bandum from Tara and doesn't check the signature, so use it only during development

GitHub and GitLab connection ​

VariableDescription
PHILLIP_SCMName of the SCM kit to force (for example kit-scm-gitlab), instead of choosing by the host of origin
PHILLIP_GITHUB_REPOowner/repo, overrides the repo inferred from origin
PHILLIP_GITHUB_APIGitHub API address, for GitHub Enterprise
PHILLIP_GITLAB_APIAPI address of a self-hosted GitLab, for example https://gitlab.example.com/api/v4
PHILLIP_SCM_OAUTH_CLIENTSJSON array of OAuth configuration for unknown servers. Tara usually provides it, so override it only during development
PHILLIP_SCM_PLUGINPath to an unreleased SCM kit directory, for development and testing
GITHUB_TOKEN, GITLAB_TOKENTokens in the environment, which take priority over saved tokens. If you change a token and see no effect, check these two variables
PHILLIP_MCP_TOKEN_CMDA JSON argv array that replaces the ph connect token --json command the SCM kit's MCP server calls to get a token

Kits ​

VariableDescription
PHILLIP_KIT_TOKENSecret (bot token, SMTP password, SCM token) for ph kit check. The command doesn't accept secrets as command-line arguments, so they don't end up in shell history

Guardrails ​

VariableDescription
PHILLIP_GUARDRAILS_POLICYName of the corporate policy package the hook server loads, default kit-policy-corporate. ph guardrails install writes this value into the service
PHILLIP_GUARDRAILS_REFRESH_SECPolicy refresh interval in seconds. Default 900, which is 15 minutes
PHILLIP_GUARDRAILS_POLICY_DIRLocal policy package directory for authoring and testing. This variable bypasses Tara, so don't use it in a real install
PHILLIP_GUARDRAILS_AUDIT_UPLOADSet on to send masked audit data to the central store. Off by default. Set it only if your organization decides to enable it
PHILLIP_GUARDRAILS_DEVICE_FILEPath of the machine file that holds the organization's device token. ph guardrails install writes it when it gets a device token, and sets this variable in the service. The hook server uses the token only when no user is signed in to Tara or the sign-in is rejected, and only toward the Tara address recorded in the file
PHILLIP_GUARDRAILS_DEVICE_TOKEN, PHILLIP_GUARDRAILS_DEVICE_ORGDevice token (tara_dev_...) and organization slug that ph guardrails install reads when neither --device-token nor --device-token-file is given. MDM packages use them so the token stays out of the process list

sudo ph guardrails install usually writes these variables into the machine's service configuration, so you rarely need to set them yourself.

Claude Code and the secret store ​

VariableDescription
PHILLIP_CLAUDE_BINPath to a Claude Code to use instead of the bundled one, for development and testing
PHILLIP_KEYCHAIN_SERVICEEntry name in the secret store, for testing without touching the real entry
PHILLIP_SECRETS_DIRStores tokens as files instead of in the secret store, for testing only
PHILLIP_DPAPI_FILEOn Windows, this is the token file encrypted per account. Phillip sets it when it runs

Variables Phillip sets when it runs Claude Code ​

When you run Claude Code through ph, Phillip sets a few variables for that session, so you don't need to set them by hand.

GroupMeaning
CLAUDE_CODE_ENABLE_TELEMETRY, OTEL_*Turn on telemetry sent to Ryoma. The data sent is described on the Data collected page
PHILLIP_TARA_URLTells Claude Code which Tara to use to get authentication headers for the marketplace and MCP
ANTHROPIC_MODELThe model from the user's configuration, set only when the project hasn't chosen a model

Don't put secrets in the repo

Variables that hold tokens, passwords, or keys must live in the environment, the secret store, or your organization's secret-management system. Don't put them in files you commit.

Further reading ​