Settings file
The CLI reads project settings from a settings file in the root of your project directory. The following file names are supported (checked in order):Intuned.jsonIntuned.jsoncIntuned.yaml/Intuned.ymlIntuned.toml
--settings-format option on supported commands to specify the format when creating or modifying the settings file.
For the full settings file schema (including the defaults block for proxy, timeouts, traces, retries, and auth session behavior), see Intuned.json reference.
Environment variables
| Variable | Description |
|---|---|
INTUNED_API_KEY | API key for authentication. When set, takes priority over browser-based login. Requires INTUNED_WORKSPACE_ID or workspaceId in settings. |
INTUNED_WORKSPACE_ID | Workspace ID. Required when using API key authentication if not set in the settings file. |
INTUNED_CHROMIUM_PATH | Path to a custom Chromium executable for the dev browser. |
INTUNED_STEALTH_CHROMIUM_PATH | Path to a Chromium executable used for stealth mode. |
INTUNED_SETTINGS_PATH | Directory for CLI settings and credentials. Defaults to ~/.intuned. |
INTUNED_EXTENSION_PATH | Path to the captcha solver browser extension. |
INTUNED_CAPTCHA_EXTENSION_PORT | Port for the captcha solver extension to communicate on. |
Authentication
The CLI supports two authentication methods, resolved in the following priority order:-
API key (
INTUNED_API_KEYenvironment variable) — authenticates using an API key. RequiresINTUNED_WORKSPACE_IDorworkspaceIdin the settings file. The API key is exchanged for a short-lived token that is cached and auto-refreshed. -
Browser-based login (
intuned login) — interactive browser-based OAuth login. Credentials are stored in~/.intuned/credentials.jsonand auto-refreshed.
Credentials storage
Browser-based login credentials are stored in:intuned login and intuned logout. Tokens are auto-refreshed when they expire.
Reference
- Overview
- Dev reference — Develop and test automations locally.
- Platform reference — Manage projects on Intuned platform.