Create, configure, push, pull, invite, manage, and remove Aether Workshop cloud libraries.
Feature Summary
Section titled “Feature Summary”Cloud libraries let teams share component libraries, Capsule libraries, dependencies, component history, Capsule history, and library structure commits through the Aether cloud API.
When to Use It
Section titled “When to Use It”- Share a library across machines.
- Let teammates use a curated hardware component set.
- Version components and Capsules in a shared package.
- Invite collaborators as Owner, Editor, or Viewer.
- Keep local work while pulling remote updates deliberately.
Create a Cloud Library
Section titled “Create a Cloud Library”- Sign in with GitHub or Google.
- Open the library/cloud management area.
- Choose a local library as the seed.
- Create a cloud package.
- Publish current component and Capsule commits.
- Push the initial library structure commit.
The local library remains available and becomes linked to the remote package.
| Role | Capabilities |
|---|---|
| Owner | Manage members, push, pull, delete cloud version, create invite links. |
| Editor | Push and pull library changes. |
| Viewer | Pull and inspect shared content. |
Owners can create 48-hour invite links for Editor or Viewer access.
Push Changes
Section titled “Push Changes”- Commit dirty component or Capsule versions first.
- Resolve remote updates.
- Add a structure commit message.
- Push.
The app blocks structure commits when required component/Capsule content commits are missing.
Pull Updates
Section titled “Pull Updates”Remote updates are explicit. The app checks for updates on startup, entering cloud/library/history views, refresh, and visible-state changes, but it does not silently overwrite local protected drafts. Pull only after reviewing local changes.
Export and Import
Section titled “Export and Import”Libraries can be packaged as .aetherlib JSON packages. Package schema v2 includes component library data, Capsule library data, dependencies, component history graphs, and Capsule history graphs.
Remove or Leave
Section titled “Remove or Leave”- Owners can delete the cloud version.
- Non-owners can leave.
- Both flows keep the local copy.
- Default API base URL is
https://api.chengxin.design. - Cloud auth uses browser login and the
aether-workshop://auth/...callback. - Tokens are stored in Keychain.
- Cloud packages are not the same as project
.aewfiles.
Why can I not push? You may be a Viewer, have an empty commit message, have unhandled remote updates, or need to commit component/Capsule versions first.
Does cloud automatically merge local drafts? No. Remote updates are explicit and protected drafts can block pull.
Can I import a shared component into another library? Yes. Component sharing supports import with overwrite or duplicate conflict handling.