The shell opens but the agent cannot start
Check that you are in the intended project and that the agent is installed inside the workspace. Install a supported one with the dev-tool manager, then run its version check in the same shell. If it starts but cannot reach its model, complete the agent's own sign-in with your model provider.
The image cannot be found
Check the image name, the full version and the Ubuntu suffix, and keep the image and the workspace options on the same release. An image already on your computer can differ from what a moving tag points to now. Tell a missing version apart from denied access or a network problem before you change the definition.
Files are not writable
Compare id inside the workspace with the owner of the affected files. The working user's numeric IDs should match your own account. Fix the IDs in the project definition and rebuild.
The Docker client cannot connect
docker --version checks only the client, while docker version also tries to reach an engine. Check whether the project asks for Docker inside the workspace, your computer's Docker, or neither (the default), then change the dockerd setting and rebuild.
Display, sound, GPU or USB is missing
These come from your computer through AIDC Launch; the image contains the libraries. Check the matching setting in the project, then run aidcx doctor and aidcx inspect on your computer to see what was actually provided. Changing the sound mode needs the workspace recreated. With USB set to dynamic, attach devices after the workspace starts.
What you getThe failing part named, and a fix that rebuilds cleanly instead of patching one container.