@Console properties are stored in configuration cache while of course not touching key or fingerprint

[Vampire]

Given a task with

@get:Console
abstract val verbose: Property<Boolean>

and

init {
    verbose.convention(project.gradle.startParameter.logLevel <= INFO)
}

If you use the configuration cache and run the task, it remembers the state.
So if you do gradlew -i myTask you get verbose output.
If you then change one of the inputs and do gradlew myTask the task is rerun and still outputs verbosely.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[bamboo]

This is still relevant.

[mlopatkin]

FWIW, it's more about "StartParameter data read at configuration time should be CC inputs" or "Have lazy changing accessors to StartParameter data". I don't think @Console is particularly special with regard to CC.