A project or file cannot be accessed
Check project scope and file access before assuming work has disappeared.
Last updated 16 September 2026
Check project scope and file access before assuming work has disappeared.
Before you start
Know the folder or file you expected to open. Sidebar entries and search results are navigation aids; the underlying file may have moved or become unavailable.
Use the active project name and file tree to check scope first. A different project folder or Solo workspace can explain why the expected file is absent.
Step by step
Confirm the active project name and any Solo scope in the workspace. A different project can legitimately show a different file tree.
Open Code and inspect the project tree. Check whether you added the repository root, a parent folder, or a nested subproject.
If search returns nothing, shorten the query and inspect its Files, Chats, Tasks, or Docs filter. Search does not include every generated directory.
If the folder is on a disconnected drive or was moved, make the correct location available and open that project folder again.
If macOS reports an access denial, review Choro’s permission for that folder and retry the specific read. Do not remove the project files as a troubleshooting step.
Report the action, expected file, exact error, and whether direct file access works if the problem remains. Avoid including private file contents unnecessarily.
What to expect
You identify a scope, location, indexing, or permission problem without discarding the original work.
Troubleshooting and useful details
A missing sidebar tool can be enabled through Manage. Removing a favorite changes navigation placement; it does not delete repository files. Assets that point to local files still need their sources to remain available.