dev-buddy-manage-presets

You can manage AI provider presets by using scripts to list, add, update, and remove entries stored at ~/.vcp/ai-presets.json. This approach handles API, subscription, and CLI types while enforcing strict validation and credential masking to prevent mismanagement.

The best way to update AI provider credentials is by modifying the presets configuration. The system masks sensitive keys during updates and validates required fields per provider type, ensuring you can safely switch providers for tasks like testing or production deployments without editing code.

Credential validation checks that all required fields for each preset type (api, subscription, cli) are present before saving. It automatically masks sensitive API keys in the configuration file to protect your credentials while allowing Dev Buddy pipelines to access the necessary authentication.

Yes, you can switch AI providers for specific pipelines without changing code by updating the preset configurations. By modifying the provider and model settings in the stored presets, you control which AI service is used for each distinct pipeline stage.

The preset management functionality is implemented via Bun scripts and preset-utils.ts. You need the appropriate runtime environment to execute these scripts, which interact with the local configuration file to enforce validation and update provider settings.

AI preset configuration fails validation when required fields for the specified preset type (api, subscription, or cli) are missing or incorrectly formatted. The strict validation mechanism ensures only complete and valid configurations are written to the presets file.