Magiccfg 1.3 Apr 2026

$ magiccfg apply --fix Checking 14 resources... [WARN] ~/.zshrc: expected mode 644, found 600 → fixed [WARN] ~/.config/nvim/init.lua: missing → restored from catalog [OK] All resources match intended state. Integrate encrypted secrets directly into your config catalog using age (modern, simple encryption). Magiccfg 1.3 transparently decrypts files matching *.age when run with the private key available via $MAGICCFG_AGE_KEY or an age agent.

The maintainers of are pleased to announce the release of version 1.3, a significant update to the cross-platform, templated configuration management tool. Magiccfg bridges the gap between simple dotfile managers and heavyweight orchestration tools like Ansible or Puppet, focusing on reproducible, human-readable configuration state across Linux, macOS, and Windows (via WSL and native PowerShell). magiccfg 1.3

magiccfg_1.3.0_checksums.txt signed with maintainer key 0x4D6C3A8F2E9B1C7A . Magiccfg – configuration as intention, not just code. $ magiccfg apply --fix Checking 14 resources

Example config.yaml :

~/.config/magiccfg/ ├── config.yaml ├── templates/ │ └── gitconfig.tmpl └── secrets/ └── github-token.age Magiccfg 1

resources: - path: ~/.ssh/id_ed25519 source: secrets/id_ed25519.age decrypt: age mode: "0600" Write custom resource types in any language that speaks JSON over stdin/stdout. Hook into check , apply , and diff phases. Plugins are discovered via ~/.config/magiccfg/plugins/ .

If you used magiccfg verify in scripts, replace it with magiccfg apply --dry-run . Inline shell commands in resources are now deprecated – see Migration Guide for the new plugin-based approach. Example: Using magiccfg 1.3 to manage a developer workstation Catalog structure: