Guides
Unregister a homebase
Review local homebase unregister, dependent projects, preserved knowledge, and optional guidance cleanup in Mindslice.
Unregister a homebase when this machine should stop using its local registration. This does not delete the homebase repository. To remove a project's shared selection rules, see disconnect a project.
The reviewed unregister workflow below requires CLI and service v0.3.0 or later. v0.2.5 has different behavior.
Before you start
Start the matching local service with mindslice service start and inspect
mindslice status. Ensure the homebase path and metadata are accessible if
you want to remove its owned guidance. Review uncommitted files and permissions.
Any dependent local project blocks unregister, even if it has another homebase. The preview lists dependent connections and their homebases. There is no automatic cascade or healthy local-only detach. Full project disconnect is a separate operation that removes shared rules; understand and approve those effects before choosing it.
Review and unregister
mindslice unregister <homebase-id>Omit the ID to choose a homebase. Review the registration, dependencies, history state, guidance and blockers. If owned guidance exists, choose separately whether to remove it. No retains all guidance and ownership records; Yes requests removal only of unchanged recorded owned guidance. Confirm the final reviewed choice. Cancelling before apply changes nothing.
| What changes | What stays |
|---|---|
| The local homebase registration; optionally approved unchanged owned guidance | Repository, knowledge, Git history, shared selection rules, project descriptors and unrelated files |
| Approved guidance removals appear as Git working-tree deletions | Modified or unowned content; no staging, commit or push |
Pending or invalid history journals and active history attempts block
unregister even if automatic history is disabled. Inspect mindslice history pending --project <connected-project-directory> --hb <homebase-id> and
reconcile safely; never clear a journal to bypass the blocker. Modified
guidance, unsafe metadata or integration locks can block its removal; choose
No to retain guidance where local unregister is otherwise allowed, or preserve
and reconcile the affected files. A missing or replaced homebase path can be
unregistered locally with guidance retained, not cleaned up.
Verify and recover
Check mindslice status and inspect the homebase files and Git changes.
After a partial result or timeout, inspect mindslice unregister --operation <unregister-operation-id> if available, current registrations and files.
Cleanup is not atomic; do not assume completed removals were rolled back.
Resolve the cause and approve a fresh review to retry.
To reuse the homebase later, follow reconnect a workspace.