Connector Config

Purpose

.envvault.json stores non-secret defaults so the CLI can infer project and profile when commands are run inside a project directory.

Config shape

{
  "schemaVersion": 1,
  "projectId": "project-id-from-envvault",
  "defaultProfile": "development",
  "requiredCliVersion": "0.22.0"
}

Behavior

• Project Detail can create or repair the file.
• Project Detail can refresh and read an existing file.
• The CLI searches upward from the current directory.
• The config does not store secret values.
• The parser rejects unsupported schema versions and missing projectId or defaultProfile values.

Why this file exists

Without .envvault.json, CLI commands need explicit --project and --profile flags. With .envvault.json, the envvault command can infer the linked project and default profile from the current folder while keeping secrets out of the config file.

Framework-aware scripts

EnvVault detects JavaScript project hints from package.json and lockfiles, then suggests runtime scripts for Next.js, Vite, React, Node.js, Bun, npm, pnpm, and yarn workflows.