aspire config set command

Name

aspire config set - Set a configuration value.

Synopsis

Aspire CLI

aspire config set <key> <value> [options]

Description

The aspire config set command sets a config value by key name.

Starting in Aspire 13.2, Aspire prefers a rooted aspire.config.json file for project-scoped configuration. The CLI can also read and write user-scoped global defaults.

• Project-scoped configuration

  Project-scoped settings live in a rooted aspire.config.json file. This replaces the older .aspire/settings.json model.

• Global configuration

  User-scoped defaults can be set with aspire config set --global .... Project-scoped settings override global values when both are present. Project-specific values such as appHost.path must be configured locally in aspire.config.json.

Arguments

The following arguments are available:

• key

  The configuration key to set.

• value

  The configuration value to set.

Options

The following options are available:

• -g, --global

  Set the configuration value in user-scoped global Aspire configuration instead of the rooted aspire.config.json file. Project-specific values such as appHost.path can’t be set globally.

• -?, -h, --help

  Prints help and usage documentation for the available commands and options.

• -l, --log-level <Critical|Debug|Error|Information|None|Trace|Warning>

  Set the minimum log level for console output. Use this option to increase diagnostics while troubleshooting or reduce output in scripted runs.

• --non-interactive

  Run the command in non-interactive mode, disabling all interactive prompts and spinners.

• --nologo

  Suppress the startup banner and telemetry notice.

• --banner

  Display the animated Aspire CLI welcome banner.

• --wait-for-debugger

  Wait for a debugger to attach before running a command.

Settings

The following config settings are available:

Logical key	Stored in aspire.config.json as	Description
appHost.path	appHost.path	Project-scoped path to the default AppHost entry point. This setting must be configured in the local aspire.config.json file.
channel	channel	Default Aspire channel used by channel-aware commands such as aspire new, aspire init, and aspire update.
features.defaultWatchEnabled	features.defaultWatchEnabled	Enable or disable watch mode by default when running Aspire applications for automatic restarts on file changes.
features.experimentalPolyglot:go	features.experimentalPolyglot:go	Enable or disable experimental Go AppHost support.
features.experimentalPolyglot:java	features.experimentalPolyglot:java	Enable or disable experimental Java AppHost support.
features.experimentalPolyglot:python	features.experimentalPolyglot:python	Enable or disable experimental Python AppHost support.
features.experimentalPolyglot:rust	features.experimentalPolyglot:rust	Enable or disable experimental Rust AppHost support.
features.polyglotIntegrationFilterEnabled	features.polyglotIntegrationFilterEnabled	Enable or disable filtering aspire add, aspire integration list, and aspire integration search results to only integrations compatible with a non-C# AppHost. Disabled by default because remote NuGet feeds don’t reliably answer the tags:polyglot query used to build the compatibility allow-list.
features.showAllTemplates	features.showAllTemplates	Show all available templates, including experimental ones, in aspire new and aspire init.
features.showDeprecatedPackages	features.showDeprecatedPackages	Show or hide deprecated packages in aspire add search results.
features.updateNotificationsEnabled	features.updateNotificationsEnabled	Enable or disable Aspire CLI update notifications.
overrideStagingFeed	overrideStagingFeed	Escape hatch that always allows the staging channel to be resolved, regardless of the running CLI’s build identity. Set this to the staging feed URL you want channel-aware commands (aspire new, aspire init, aspire update) to use, for example: aspire config set -g overrideStagingFeed <feed-url>. Without this setting, --channel staging only resolves on stable or staging Aspire CLI builds — daily, local, and per-PR builds refuse it and report the recovery options.