AI-generated code fails on another machine: how do you check dependencies and startup instructions?

Record how the failing machine actually starts the program

This applies to failed imports, unavailable commands and author-machine-only startup. Record the operating system, interpreter or runtime, working directory and first meaningful error. Missing models or static assets may also be responsible; not every failure is a missing package. Do not bundle real secrets or private machine paths as a repair.

Compare runtimes, dependency declarations and required assets

Compare manifests and lockfiles and distinguish development from runtime dependencies. Ensure the executing environment is the one where dependencies were installed. Inspect absolute paths and required variables and list separately downloaded public assets. Import names may differ from distribution names; inspect actual origins instead of installing similarly named packages blindly.

Rebuild from recovery instructions in a clean environment

Install with the project’s locked process in an independent environment or clean copy, then follow recovery instructions for startup and a minimal functional check. Add genuinely missing packages to the formal manifest and state supported runtime ranges. For external services, provide variable names and acquisition instructions with placeholders, never personal tokens, login caches or the author’s complete environment.

Confirm a new machine runs without manual missing-package fixes

Rebuild without inheriting the author’s global packages and verify installation, startup and essential actions. Check instructions for missing directories, asset paths and preparation steps and make errors identify absent configuration names. Successful installation alone does not establish a working application; a window opening while core features fail is not complete runnable delivery.

This article installed nothing on another machine or copied a personal environment. Lockfiles cannot resolve every system-library or hardware difference, so state platform limits and external requirements. Do not add secrets to reproduce an environment. If dependencies require restricted access or authorization, document recovery prerequisites rather than hiding them in an assumed development cache.