Troubleshooting

sbxm refuses a mutation when ownership, external state, or user intent cannot be established safely. Start with the narrowest read-only diagnosis:

1. Run sbxm status --global for host and Docker Sandboxes problems.
2. Run sbxm status <project-id> for project artifacts, credentials, repositories, and worktrees.
3. Follow the relevant safety refusal guidance.
4. Re-run the original command after the observed condition is fixed.

Choose a scope

• Diagnose the host — platform, Docker, login, network, and SSH.
• Diagnose a project — registry, image, sandbox, secret, repository, and worktree.
• Resolve safety refusals — dirty work, collisions, active sessions, and ownership.