v1.4.0CLILatest
•1 min read

Local Per-Project Config (.apivault.json) & Hierarchical Scopes

Bind project context and CLI settings directly to your local project directory via .apivault.json, eliminating the need to switch projects when changing directories, while retaining global fallback configuration.

#What's Changed

  • [Feature] Local project directory configuration: save project bindings, default run commands, environments, and vault keys directly in .apivault.json inside your project root.
  • [Feature] Hierarchical config scopes: all apivault config commands now support --local (-l) and --global (-g) flags with local settings automatically taking precedence over global settings.
  • [Feature] Enhanced apivault projects use <id>: defaults to linking the current directory locally via .apivault.json, with --global available for system-wide defaults.
  • [Feature] New apivault link <id> and apivault unlink commands: quickly bind or unbind the current directory to an ApiVault project.
  • [Feature] New apivault projects current command: inspect the currently resolved active project ID along with its resolution source.