The Social post editor now uses a searchable, paginated space picker for Orbit targets — so hubs with thousands of spaces stay fast without loading the full list upfront.
What we shipped
Orbit connect and per-target spaceSlug in the Social API let teams publish into hosted hubs like Orbit. This release fixes the dashboard half of that workflow for large instances.
Searchable space picker in the post editor
When a draft targets a connected Orbit account, the Space field is now a searchable picker instead of free text:
Opens on demand — an untouched editor makes no hub requests until you interact with the picker
300ms debounced search — each new query restarts at offset 0
Load more appends the next page with a showing X of Y count
Default space clears back to the slug saved at connect time
Superseded responses are ignored so a slow earlier page cannot overwrite a newer search
The Connect Orbit dialog (opened from Add → Orbit on Accounts) still uses a text field for the default space — at connect time there is no account to query yet.
Why we built it this way
Self-hosted hubs can expose hundreds or thousands of spaces. Fetching the full list on every editor open would be slow and wasteful. Server-driven search keeps the UI responsive and matches how operators actually find a space — by name, not by memorizing slugs.Agents continue to set spaceSlug on each supahub target in POST /api/v1/social/posts — the picker is for human reviewers in the dashboard.
Try it
Connect a hub on Dashboard → Social → Accounts (Add → Orbit).
Create or expand a post and check a Orbit account under Publish to.
Open the Space picker, search for a space name, and select it — or leave Default space.
