First run#

On the final first-run screen choose Import Pair Set… and select a canonical JSON file. Ster Desktop sends only the path, as the body of ster request workspace/import-pairs; the Rust binary validates and persists it. The walkthrough closes only after an imported or unchanged response, then loads the accepted destination into the pair editor.

Import again#

Open Workspace and first run at the bottom of the pair workflow and choose Import pair set…. The row reports imported, unchanged, conflicting, or rejected, including the retained destination or refusal reason. Show first-run guide again replays the same import action.

Retention and safety#

Files live in Ster’s XDG data directory and remain across app restarts. Existing sets are preserved by default, repeated canonical content is idempotent, unknown fields are rejected, and an invalid input cannot partially update the manifest. Desktop never parses or rewrites the source itself.