The CLI reads these variables from its process environment. Set them before running deeep. For example, allow 15 minutes for a Storybook build on macOS/Linux:
In PowerShell:
These timeouts do not configure static-file uploads. Storybook upload requests use a 10-second connection timeout and 120-second read timeout.

​
Credentials and project files

Authentication stores the access token, refresh token, and email in the operating system’s keyring through Python keyring, under the deeep service. deeep logout removes these entries. They are not stored in deeep.json. A working, accessible keyring backend is required, including in headless environments; the CLI has no token or noninteractive login flag. deeep.json stores the project link and discovery settings. Configuration is read from the current working directory, so run project commands from the repository root where that file lives. Index paths are resolved relative to the Git root. Successful commands can rewrite deeep.json, including account commands; it is not exclusively written by init. Commit deeep.json when the team should share the setup. The generated .deeep.index.json can be ignored by Git. Review sync prerequisites for the source files that must be committed.

​
Optional telemetry

With a nonempty DEEEP_MIXPANEL_TOKEN, the CLI uses the account email as the Mixpanel identifier, updates a CLI-user profile property, and reports a Sign In event containing the email, platform, and sign-in method. This telemetry is identifiable, not anonymous. It does not send source files or authentication tokens to Mixpanel. To disable this client for a shell session:
Component manifests and optional Storybook build uploads are separate from sign-in telemetry. See Component index and sync data and Storybook hosting.