Add a Saved Project

Add project creates a cloud project from saved local files. It does not move or delete your original design.

Before adding

Save the editor changes you intend to include. If the editor and disk differ, reconcile them first rather than overwrite newer files.
Locate the saved .kicad_pro, its schematic hierarchy, board if present, paired .xo files and required local libraries.
Choose who should receive the project. Personal Cloud (only you) is account-scoped cloud storage; Team shares with authorized team members.
Review .trace/context.md and other included files for confidential content. Personal .trace/rules.md, prior private chats and local history are not silently reassigned to the cloud project.

Add the project

Choose Add project in Workspaces, or Add to Workspaces in the project tree when offered.
Check Source. Use Choose saved project… for a different .kicad_pro.
Review included/excluded files under Details. Resolve missing required files; use Prepare files if older KiCad files need conversion.
Choose Personal Cloud (only you) or a team you can add to, then review the project name.
Click Add project and follow preparation, upload and cloud-save progress.
After Project added, choose Open project when ready to edit the cloud copy. Check the project and branch that actually open.

Preparation and conversion operate on separate copies. The source ignore rules, native design and drawings remain intact. A valid schematic-only project does not need an invented empty PCB.

Understand file findings

Missing electrical dependencies block addition. A stock 3D-library requirement is a different finding, not proof that electrical data is missing. Review the named dependency and correct the source or supported library setup before preparing again.

Ignore rules use .traceignore, not .gitignore. Review exclusions rather than hiding required files to make preparation pass. Included .xo files contain authored drawings and placement; they are not disposable.

Exclusion counts describe observed entries. A pruned directory is not a recursive count of every file inside it. A truncated inventory is not a complete confidentiality review.

Cloud added does not mean locally open

Project added confirms cloud publication. Open may still fail or need attention. Use Try opening again for that same project, not another Add. Keep the original local project available until you have inspected the opened copy and its saved files.

In the compatible flow, a confirmed completed addition does not require Done before adding another project. Pending opening or uncertain publication is different: use the matching recovery controls rather than bypass the earlier operation.

If adding does not finish

Closing the window is not cancellation. An unfinished addition appears under Continue adding, named separately from a newly selected source. Use Continue to check that original addition's saved progress.

If the reply was lost, the outcome remains unknown. Do not add another copy or select a new request to work around it. Repeated recovery without a clear result needs investigation, not repeated blind retries.

Use Cancel adding project to request cancellation. Wait for a confirmed outcome; a lost cancellation reply does not prove nothing was uploaded or saved. If confirmed cancellation leaves cleanup unfinished, use Finish cleanup. Do not manually delete uncertain recovery files.

Next: Save and sync or recover the original operation.