Guides
Disconnect a project
Review Mindslice project disconnection, shared rule removal, preserved files, and ownership-aware cleanup before confirming.
Use full disconnect when a project should no longer use its attached homebases. To remove only a homebase registration, see unregister a homebase.
The reviewed full-cleanup workflow below requires CLI and service v0.3.0 or later. v0.2.5 has different disconnect behavior.
Before you start
Start the matching local service with mindslice service start. Ensure the
project and every attached homebase directory and manifest are accessible and
inspectable. Review uncommitted changes and use appropriate Git permissions.
Run mindslice status to identify the project connection ID.
Full disconnect removes the stable project's selection and routing entry from every attached homebase, not just one local attachment. Other local checkouts with the same project ID lose that selection. Other machines see shared-rule changes only after normal Git propagation; Mindslice does not stage, commit, push or synchronize them.
Review and disconnect
mindslice disconnect <project-connection-id>Omit the ID to choose a registered checkout. Review the project, paths, homebases, affected files, retained content and blockers. Approve recorded integration cleanup separately if offered, then confirm the shared-rule effects and full disconnect. Declining either approval or cancelling before apply changes none of the scopes.
| What changes | What stays |
|---|---|
| Shared project entries in attached homebases, verified managed views, unchanged recorded owned guidance and exact owned hooks | Project directory and descriptor, knowledge, homebase registrations and unrelated settings |
| Empty integration directories may be pruned | Modified or unowned content is not force-deleted |
Modified owned guidance, conflicting hooks, unsafe paths or unavailable
homebase metadata can block full cleanup. Restore access or preserve and
reconcile the conflicting files before reviewing again. mindslice cleanup
is a separate local-only stale-registration recovery, not full disconnect.
Verify and recover
Check mindslice status, the affected homebase manifests and project files;
review any Git changes before sharing them. After a partial result or timeout,
inspect mindslice disconnect --operation <disconnect-operation-id> if
available, status and the listed files. Multi-file cleanup is not atomic:
completed removals are not rolled back and failures retain the connection.
Resolve the blocker and approve a fresh preview before retrying.
If your goal is to remove a local homebase registration afterward, review unregister a homebase.