Guides
Reconnect a workspace
Reconnect an existing Mindslice homebase and project checkouts on another machine while preserving shared identities and context.
Bring an existing homebase and its project context to this machine without starting over. For a genuinely new homebase, use getting started.
This workflow requires CLI and local service v0.3.0 or later; v0.2.5 does not provide this guided multi-project workflow.
Before you start
Download or otherwise obtain the homebase and application checkouts using
your usual Git or filesystem tools. Git can preserve committed IDs and rules,
but local registrations and paths are machine-specific. Starting the service
does not connect downloaded folders. Install a matching CLI and service, start
the service with mindslice service start, and ensure the directories and
their metadata are accessible. Use your normal Git permissions and review
uncommitted changes before proceeding.
For example, the homebase may be at /directory/1/homebase, with application
checkouts at /directory/2/project1 and /directory/1/project2. These are
examples; use your own absolute paths.
Review and connect
mindslice init --connect-projects /directory/1/homebaseReview the existing homebase identity and registration. Existing metadata and rules are reused, not reinitialized. A homebase registered at another path requires a separate reviewed relocation; malformed or conflicting metadata must be repaired. The command accepts a local directory and does not clone projects.
Inspect discovery's roots, limits, candidate paths, completeness and issues. Choose each checkout explicitly, even for one match; for missing or ambiguous results provide the matching absolute path or skip that project. A missing descriptor may be recovered only after selecting the existing manifest ID and approving its creation. A malformed or mismatched descriptor is not overwritten. If the manifest is empty, choose projects explicitly rather than assuming nearby repositories were discovered.
Review each proposed descriptor, homebase reference and new selection rule, then the connection list. Existing other-homebase attachments and views stay. Approve optional guidance and reminder hooks separately; choosing No retains the connection. Cancel before a stage applies leaves that stage unchanged, not earlier approved work. A project with no selection rule exposes no documents and is reported as unhealthy or partial.
| What changes | What stays |
|---|---|
| Approved local registrations and managed views; any separately approved metadata or rules | Existing identities, other homebase attachments, unrelated rules and knowledge |
| Optional approved guidance and hooks | Modified or unowned guidance and existing files not approved for change |
Verify and recover
Run mindslice status and, from each connected project, mindslice knowledge tree. Check that views are healthy and contain the intended pages. Inspect
changed descriptors, manifest and guidance with Git; no automatic commit,
push or synchronization occurs.
If discovery is incomplete or a checkout is skipped, resolve the issue or
provide its path in a fresh session. After interruption or a partial result,
inspect mindslice init --operation <setup-operation-id> if an ID was
reported, plus status and the affected files. A timeout is not proof of
rollback; reconcile completed work and approve a fresh preview to retry.
To remove a connection instead, see disconnect a project.