Settings, credentials and interactions
Separate machine-local settings from transferable project data.
AlphaUse local settings for endpoints, credentials and other machine-specific configuration. Use project settings or versioned project state for data that belongs to the project's behavior.
Safe writes and interactions
Core owns versioned settings operations and protected storage. Expose validation and supported commands through descriptors; preserve stored secrets when the user leaves a protected field unchanged.
Request password, OAuth, information, clipboard or schema-form interactions through the applicable public host contracts. Keep sensitive values out of display descriptors. Respect cancellation, expiration, revocation and the absence of a capable requesting client.
Use the supported runtime local-settings change contract for refreshed credentials instead of writing Core's settings files yourself.
Quick connections
Optional IServiceConnectionPlugin contributes stable named connections to Core Settings. Its connect operation restores saved configuration; it must not launch OAuth, install dependencies or clear credentials.