Adding a bucket used to offer two doors that did nearly the same thing. Now there are two that don't overlap: Discover finds what a credential can see, and Create Bucket makes a new one.

Credentials that legitimately can't list buckets — Google Cloud Storage, scoped R2 tokens, least-privilege AWS policies — get a guided card with an inline "add it by name" form instead of an empty list. A bucket added by name is verified before it's registered, so a typo returns a clear error rather than a bucket that appears to exist and fails on first use.

Other rough edges from the same release: a bucket deleted at the provider now says so plainly, browser uploads apply their CORS rule automatically on first use when none exists, and creating a bucket on a provider without versioning no longer offers it.