Skip to content

CLI › Profiles & Config

Profiles & Config

Named profiles let you maintain separate configurations for different networks, wallets, and use cases. Secrets are stored separately from general config.

Create a Profile

Create named profile

npx @trucore/atf@1.5.1 profile create --name staging

Creates a new profile directory at ~/.atf/profiles/staging/. Config and secrets are stored in separate files within that directory.

Switch Profiles

Switch active profile

npx @trucore/atf@1.5.1 profile switch staging

All subsequent commands use the staging profile until you switch again.

Set and Read Config

Set a config value

npx @trucore/atf@1.5.1 config set network devnet

Read a config value

npx @trucore/atf@1.5.1 config get network

Configuration values are plain text and safe to commit to version control. Secrets like API keys use a separate, gitignored secrets file.

Secrets Handling

Secrets (API keys, private key paths) are stored in ~/.atf/profiles/<name>/secrets.json, which is excluded from version control by default.

Config values go in config.json. This separation ensures you can safely share or commit your config without leaking sensitive data.

List All Profiles

List profiles

npx @trucore/atf@1.5.1 ls

Shows all configured profiles and highlights the currently active one. See also whoami & ls.

Common Flags

FlagDescription
--name <profile>Specify the target profile for create/delete operations.
--profile <name>Override the active profile for any command.
--jsonOutput results as JSON.