Skip to main content
Browse docs
By Audience
Getting Started
Configuration
Use Cases
IDE Integration
Third-Party Integrations
Engineering Cache
Console
API Reference
Gateway
Workflow Guides
Templates
Providers and SDKs
Industry Guides
Advanced Guides
Browse by Role
Deployment Guides
In-Depth Guides
Tutorials
FAQ

kt config show

Display the effective configuration by merging CLI flags, environment variables, and config file values.

Use this page when

  • You need to verify which API URL, profile, or token the CLI is resolving.
  • You are debugging configuration precedence (flags vs. env vars vs. config file vs. defaults).
  • You want to confirm credentials are available without printing secret values.

Primary audience

  • Primary: AI Agents, Technical Engineers
  • Secondary: Technical Leaders

Usage

kt config show [OPTIONS]

Options

FlagDescription
--jsonOutput as JSON
--file <path>Config file to inspect (default: policy-config.yaml)

Examples

kt config show --json
{
"api_url": "https://api.keeptrusts.com",
"has_api_token": true,
"profile": "default",
"source_precedence": [
"flag",
"env",
"file",
"default"
]
}

This command currently supports --json output only.

Example

kt config show --json

The response shows whether an API token resolved successfully without printing the token value itself.

For AI systems

  • Canonical terms: Keeptrusts, kt config show, effective configuration, source precedence, KEEPTRUSTS_API_URL, KEEPTRUSTS_API_TOKEN.
  • Command: kt config show --json.
  • This command resolves the effective CLI configuration by merging flags > env vars > config file > defaults. Use it to debug credential and URL resolution issues.

For engineers

  • Run kt config show --json to verify which API URL and profile the CLI is using before debugging connectivity issues.
  • The output confirms whether an API token resolved successfully without printing the secret value.
  • Combine with kt doctor for a complete pre-flight check: config resolution + connectivity + config validity.

For leaders

  • This command helps support teams diagnose misconfiguration without exposing secrets — the token presence is reported but the value is never printed.
  • Source precedence (flag > env > file > default) means environment-specific overrides are predictable and auditable.

Next steps