aam config set¶
Configuration
Synopsis¶
Description¶
Set a configuration value in the global AAM configuration file. Supports both top-level and nested configuration keys using dot notation.
Changes are saved to ~/.aam/config.yaml and apply immediately to all subsequent commands.
Arguments¶
| Argument | Required | Description |
|---|---|---|
| KEY | Yes | Configuration key (dot-notation for nested keys) |
| VALUE | Yes | Value to set |
Options¶
This command has no command-specific options.
Examples¶
Example 1: Set Default Platform¶
Output:
Example 2: Set Author Name¶
Output:
Example 3: Set Author Email¶
Output:
Example 4: Enable Security Feature¶
Output:
Example 5: Set Multiple Values¶
aam config set default_platform cursor
aam config set author.name "Jane Smith"
aam config set author.email "jane@example.com"
Output:
✓ Set default_platform = cursor
✓ Set author.name = Jane Smith
✓ Set author.email = jane@example.com
Example 6: Invalid Key¶
Output:
Example 7: Nested Key Error¶
Output:
Exit Codes¶
| Code | Meaning |
|---|---|
| 0 | Success - value set |
| 1 | Error - invalid key or unsupported depth |
Configuration Keys¶
Top-Level Keys¶
| Key | Type | Description |
|---|---|---|
default_platform | string | Default deployment platform (cursor, copilot, claude, codex) |
Author Section¶
| Key | Type | Description |
|---|---|---|
author.name | string | Default author name for new packages |
author.email | string | Default author email |
Security Section¶
| Key | Type | Description |
|---|---|---|
security.require_checksum | boolean | Require checksum verification for installs |
security.require_signature | boolean | Require package signatures (future) |
Value Types¶
The command automatically converts values to the appropriate type:
Boolean Values¶
aam config set security.require_checksum true
aam config set security.require_checksum false
aam config set security.require_checksum 1 # Converted to true
aam config set security.require_checksum 0 # Converted to false
aam config set security.require_checksum yes # Converted to true
String Values¶
Quotes are optional but recommended for values with spaces.
Integer Values¶
Related Commands¶
aam config get- Get configuration valuesaam config list- List all configuration
Notes¶
Configuration File¶
Changes are saved to ~/.aam/config.yaml:
default_platform: cursor
author:
name: John Doe
email: john@example.com
security:
require_checksum: true
require_signature: false
Dot Notation¶
Use dots to access nested keys:
author.name→config.author.namesecurity.require_checksum→config.security.require_checksum
Project vs. Global Config¶
aam config set modifies the global configuration in ~/.aam/config.yaml.
Project-level configuration (./.aam/config.yaml) is not currently supported via CLI but can be created manually.
Quoting Values¶
Quote values containing spaces or special characters:
Boolean Conversion¶
Boolean values accept multiple formats:
true,false1,0yes,no- Case insensitive
Verification¶
After setting, verify the change:
aam config set default_platform cursor
aam config get default_platform
# Output: default_platform = cursor
Or list all config:
Resetting to Defaults¶
To reset a value, set it back to the default:
aam config set default_platform cursor # Default
aam config set security.require_checksum false # Default
Or edit ~/.aam/config.yaml and remove the line.
Configuration Precedence¶
Configuration sources (highest to lowest priority):
- Command-line flags
- Environment variables
- Project config (
./.aam/config.yaml) - Global config (
~/.aam/config.yaml) - Built-in defaults
Common Settings¶
Set default platform:
Set author for new packages:
Enable security features:
Unsupported Keys¶
Some configuration cannot be set via CLI:
registries- Useaam registry add/removeinsteadactive_platforms- Planned for future versions
Max Depth¶
Configuration keys support up to 2 levels:
- ✓
key- Valid - ✓
section.key- Valid - ✗
section.subsection.key- Not supported
Team Configuration¶
For team setups, document recommended settings: