Skip to main content

Usage

pm-auto config-path
Alias: cp You can use either command:
pm-auto config-path
pm-auto cp

What it does

The config-path command reads ~/.pm-auto/settings.json and displays the absolute path to your PM-Auto configuration file.

Examples

Display the config path

pm-auto config-path
┌  pm-auto 

◇  Config Path: /Users/username/projects/myapp/pm-auto.json

Using the alias

pm-auto cp
┌  pm-auto 

◇  Config Path: /Users/username/projects/myapp/pm-auto.json

When no config is set

If you haven’t set a config path yet:
pm-auto config-path
┌  pm-auto 

◇  Run `pm-auto config <path>`, where <path> is the path to your config file
✖  Config file path not set

When to use it

Use pm-auto config-path when you:
  • Want to verify which config file PM-Auto is using
  • Need to check if a config path has been set
  • Are debugging issues with preset loading
  • Want to confirm the absolute path to your config
  • Are documenting your PM-Auto setup for team members

Example workflow

# Check current config path
pm-auto config-path

# Update if needed
pm-auto config ./new-config.json

# Verify the change
pm-auto config-path

# List presets from the new config
pm-auto list

Where the config path is stored

The config path is stored in:
~/.pm-auto/settings.json
You can also check this file directly:
cat ~/.pm-auto/settings.json
{
  "configPath": "/Users/username/projects/myapp/pm-auto.json"
}
The displayed path is always an absolute path, even if you set it using a relative path with pm-auto config.

Build docs developers (and LLMs) love