Config Management¶

Lango stores all configuration in encrypted profiles within ~/.lango/lango.db. The config command group manages these profiles.

lango config <subcommand>

lango config list¶

List all configuration profiles with their status.

lango config list

Output columns:

Example:

$ lango config list
NAME       ACTIVE  VERSION  CREATED              UPDATED
default    *       1        2026-01-15 10:00:00  2026-02-20 14:30:00
staging            1        2026-02-01 09:00:00  2026-02-01 09:00:00

lango config create¶

Create a new configuration profile with default values or a preset template.

lango config create <name> [--preset <name>]

Without --preset, the profile is created with Lango's default configuration. Use lango settings or lango onboard to customize it. With --preset, the profile starts from a purpose-built template.

Example:

$ lango config create production
Profile "production" created with default configuration.

$ lango config create research-bot --preset researcher
Profile "research-bot" created from preset "researcher".

lango config use¶

Switch the active profile. All subsequent commands will use the selected profile's configuration.

lango config use <name>

Example:

$ lango config use staging
Switched to profile "staging".

lango config delete¶

Delete a configuration profile. Prompts for confirmation unless --force is specified. The confirmation prompt is driven through the Cobra command input/output streams so wrappers and test harnesses can capture or drive the interaction via cmd.OutOrStdout() and cmd.InOrStdin().

lango config delete <name> [--force]

Examples:

# Interactive confirmation
$ lango config delete staging
Delete profile "staging"? This cannot be undone. [y/N]: y
Profile "staging" deleted.

# Non-interactive
$ lango config delete staging --force
Profile "staging" deleted.

lango config import¶

Import a plaintext JSON configuration file into an encrypted profile. The source file is deleted after successful import for security.

lango config import <file> [--profile <name>]

Example:

$ lango config import ./config.json --profile production
Imported "./config.json" as profile "production" (now active).
Source file deleted for security.

lango config export¶

Export an encrypted profile as plaintext JSON to stdout. Requires passphrase verification (handled by the bootstrap process).

lango config export <name>

Example:

$ lango config export default
WARNING: exported configuration contains sensitive values in plaintext.
{
  "server": {
    "host": "localhost",
    "port": 18789
  },
  ...
}

The exported JSON contains sensitive values (API keys, tokens) in plaintext. Handle with care and do not commit to version control. lango config export emits a plaintext backup by design. lango config get --output json emits valid pretty-printed JSON on the Cobra command output stream, but redacts sensitive values by default unless --show-secrets is passed.

You can redirect the output to a file:

$ lango config export default > backup.json

lango config get¶

Read a configuration value by dot-notation path. This is a read-only command and does not require editing the profile.

lango config get <dot.path> [--output plain|json] [--show-secrets]

The command writes through the Cobra command output stream, and --output accepts only plain or json. Unknown values fail before the active config is loaded. Sensitive scalar paths and nested sensitive fields inside object or map reads are redacted by default. Use --show-secrets only when you intentionally need to inspect raw stored credentials.

Examples:

$ lango config get agent.provider
anthropic

$ lango config get p2p.enabled
false

$ lango config get providers.openai.apiKey
<redacted>

$ lango config get providers.openai.apiKey --show-secrets
sk-...

$ lango config get agent --output json
{
  "provider": "anthropic",
  ...
}

lango config set¶

Set a configuration value by dot-notation path. This is a profile-modifying command and therefore requires bootstrap/passphrase verification.

lango config set <dot.path> [value] [--from-env ENV]

Examples:

$ lango config set agent.provider openai
Set agent.provider = openai

$ lango config set p2p.enabled true
Set p2p.enabled = true

$ lango config set providers.openai.type openai
Set providers.openai.type = openai

$ OPENAI_API_KEY=sk-... lango config set providers.openai.apiKey --from-env OPENAI_API_KEY
Set providers.openai.apiKey = <redacted>

lango config keys¶

List available configuration keys derived from the config schema. Optionally filter by a dot-path prefix.

lango config keys [prefix]

Examples:

$ lango config keys
agent.provider
agent.model
...

$ lango config keys agent
agent.provider
agent.model
agent.temperature

$ lango config keys providers
providers
providers.<name>.apiKey
providers.<name>.baseUrl
providers.<name>.type

$ lango config keys mcp.servers
mcp.servers
mcp.servers.<name>.env.<key>
mcp.servers.<name>.headers.<key>
...

Map-backed configuration keys use placeholders in discovery output. <name> is the dynamic provider, server, mode, or auth provider name. <key> is a dynamic string-map key such as an MCP environment variable or HTTP header name.

lango config validate¶

Validate the active configuration profile against Lango's schema rules.

lango config validate

Example:

$ lango config validate
Profile "default" configuration is valid.

If validation fails, the command prints the specific errors and exits with a non-zero status code.