DevSpace Support

DevSpace is a local-first developer storage and environment manager for Windows. It helps users discover developer-tool storage, review reclaimable space, safely clean supported regenerable data, relocate selected supported storage roots, and recover interrupted relocation operations.

Supported platform

DevSpace 1.0 is designed for Windows x64.

The application is local-first and does not require a DevSpace account or cloud backend.

What DevSpace 1.0 supports

DevSpace includes discovery and storage analysis for supported developer ecosystems including:

• Gradle
• npm
• pnpm
• Yarn
• Android SDK
• Android Virtual Devices
• Flutter SDK
• Dart / Pub Cache

Feature support is intentionally provider-specific. A provider being discoverable or scannable does not automatically mean every cleanup or relocation operation is supported.

Relocation support in DevSpace 1.0

DevSpace 1.0 supports relocation only for selected provider-owned storage roots, including supported flows for:

• Gradle user home
• npm cache
• Dart / Pub cache
• Android Virtual Device storage

DevSpace does not provide arbitrary folder relocation.

Android SDK relocation is not supported in DevSpace 1.0.

Before using Cleanup

Cleanup is permanent and does not use the Windows Recycle Bin.

Before cleaning:

1. Review the exact provider, path, classification, and estimated reclaimable allocation.
2. Close developer tools that may actively use the selected cache.
3. Use Safe to clean items first.
4. Treat Review before cleaning items as optional and potentially disruptive to offline work or future rebuild/download time.

5. Do not attempt to bypass a blocked or protected classification.

DevSpace revalidates supported targets immediately before deletion. If the target has changed, become ambiguous, or cannot be proven safe, the operation may be blocked or reported as a partial failure.

Before using Move & Relocate

Relocation changes where a supported developer tool stores selected data.

Before relocation:

1. Close active builds and developer tools using the selected provider.
2. Choose a fixed, writable local drive.
3. Use an empty destination path whose direct parent already exists.
4. Review every validation check before executing.

5. Do not continue if a mandatory validation check fails.

DevSpace uses staging, verification, provider configuration changes, rediscovery, source-retirement validation, and durable recovery journals.

If DevSpace cannot prove that a destructive step is safe, it is designed to stop rather than guess.

Recovery Center

If DevSpace detects an interrupted relocation, it may block new Scan, Cleanup, and Relocation operations until the previous operation is resolved.

Depending on the verified state, Recovery Center may offer:

• Resume — only when the operation can be safely continued.
• Roll Back — only when a safe rollback can be proven.
• Inspect — shows the observed state and why an action is or is not available.
• Mark Manually Resolved — acknowledgement only. It does not perform filesystem or provider-configuration mutation.

Do not manually delete a relocation staging folder while an unresolved operation is still being assessed unless Mokaio support has specifically instructed you to do so.

Common troubleshooting

A developer tool is not detected

1. Confirm the tool is installed and works from a new Windows terminal.
2. Restart terminals after changing environment variables.
3. Use Refresh discovery.
4. If necessary, close and reopen DevSpace.

5. Check whether the provider's storage path is still shown even when the executable itself is not detected.

Discovery status and storage ownership are separate concepts; a storage location may exist even if the executable is not currently discoverable.

A scan does not show expected storage

1. Confirm the relevant provider is enabled in Settings → Scanning.
2. Run Refresh discovery.
3. Start a new scan.
4. Confirm the storage path belongs to a supported provider.

5. Remember that project discovery only uses project roots explicitly added by the user.

Cleanup is blocked

A blocked cleanup is normally a safety decision, not something to bypass.

Common reasons include:

• The path changed since the scan.
• Ownership cannot be proven.
• The target is protected or not managed.
• The scan result is incomplete.
• Files are inaccessible or actively changing.
• Filesystem topology or identity changed.

Run a fresh scan and review the reported reason.

Relocation validation fails

Check the validation list in Move & Relocate.

Common causes include:

• Source does not exist.
• Destination already exists.
• Destination parent does not exist.
• Destination is on an unsupported drive/filesystem.
• Source or destination path identity cannot be proven.
• A junction, symlink, or reparse-point condition makes the path ambiguous.
• Insufficient free space.
• Provider-specific destination requirements are not satisfied.
• Relevant processes are active.
• The provider configuration changed after the plan was created.

Do not create, delete, or rename paths merely to force a failed plan to execute. Correct the reported condition and validate again.

DevSpace restarted after a crash or forced termination

Open Move & Relocate → Recovery Center.

Do not delete source, destination, or staging directories until Recovery Center has inspected the operation.

If DevSpace can prove a safe recovery path, it will expose the corresponding action. If it cannot prove safety, it may require manual inspection instead.

An operation says Manual attention

Use Inspect first.

Manual attention means DevSpace could not prove that an automatic destructive recovery action was safe.

Mark Manually Resolved is an acknowledgement action only. It does not delete files, move files, restore configuration, or perform a hidden cleanup.

Local database and logs

DevSpace stores its database and diagnostic logs locally.

The exact paths for the current installation are displayed in:

Settings → Privacy

You can also use Open log folder from Settings when available.

Reporting a problem

Email:

support@mokaio.store

Suggested subject:

DevSpace Support — [short description]

Please include:

• DevSpace version and build number.
• Windows version.
• Whether DevSpace was installed through MSIX/Store or run as a local release build.
• The affected provider, such as npm or Gradle.
• What operation you were performing: Scan, Cleanup, Relocation, or Recovery.
• The exact error or safety message shown by DevSpace.
• Steps that reproduce the issue.
• A screenshot when useful.
• Relevant DevSpace log excerpts.

Please remove passwords, API keys, access tokens, private source code, and other secrets before sending diagnostic material.

Safety-related support requests

If a Cleanup, Relocation, or Recovery operation produces an unexpected state:

1. Stop performing additional destructive operations.
2. Do not manually delete the source, destination, or DevSpace staging directory.
3. Do not change the affected provider configuration unless instructed.
4. Take screenshots of the current DevSpace state.
5. Preserve the local DevSpace logs.

6. Contact **support@mokaio.store**.

This gives support the best chance to determine the current safe state without losing recovery evidence.

Privacy

Read the DevSpace Privacy Policy:

https://www.mokaio.store/privacy/devspace

Contact

Mokaio Email: support@mokaio.store Website: https://www.mokaio.store