Missing files or folder
- Confirm the Code session’s displayed working folder.
- Check that the folder still exists and any external drive is mounted.
- Use Open folder or Open another folder to select the intended location.
- Verify whether the Files view is filtering loaded or changed files.
- For an archived session, restore it before trying to edit or send a new request.
A previous-session reference does not change the active folder. Avoid recreating a missing repository until you know whether it was moved or is simply unavailable.
Terminal or Git failure
Check the terminal’s working directory and whether its shell exited. A missing command can reflect PATH inherited when Rudr started; fully reopen the app after an external tool installation.
If Git says Not a git repository, open the actual repository. For push, sync, or pull-request errors, check the remote, branch, and GitHub/Git authentication. Review staged and unstaged changes before retrying. Do not reset dirty files merely to clear a UI error.
Browser cannot reach a preview
Confirm that the real server is running and use the port it printed. Inspect the Terminal if the process exited. For agent inspection, enable Coding agent browser tools and use a loopback/local-preview URL; manual remote browsing and agent tools have different boundaries.
Try a page reload or a specific site-permission correction before Reset browser data. A full reset closes tabs and clears the workspace browser’s sign-ins, storage, cache, permissions, and restore history.
Panel or worktree seems missing
Look through existing tabs and resize narrow panes. Single-instance Files, Git, Side chat, and Subagents may already be open elsewhere. Check Command Center → Worktrees for the actual checkout and its status before cleanup.
Use Diagnostics to capture the error and tabs and panels to restore a useful arrangement.