You do not need to copy my Windows setup line for line to follow this series.
With active files copied and their permissions checked, I can choose where my development tools will run. I want to know what that workspace can reach.
My Windows 11 Pro plan uses WSL2, the Windows Subsystem for Linux. It lets me run a Linux workspace without replacing Windows. Ubuntu is the version of Linux used.
That gives me a place for code while keeping my Windows applications. Documents and design work will live under C:\Work. Linux code projects will live under ~/projects inside Ubuntu, with only the needed files passed between them.
Mac users can run many development tools directly on macOS. Linux users can work in their existing system. Both can add a container or virtual machine when a project needs more separation. The supported approach depends on the particular AI tool.
For a Chromebook, tablet, or another browser-focused device, a hosted development workspace may be an option. Check tool support, pricing, account access, and where the files are stored before choosing one. A remote workspace still needs sensible permissions.
One Windows detail is worth understanding. Turning off WSL’s automatic connection to Windows drives reduces routine exposure. It does not make those drives impossible to connect manually. The permissions on the Windows side still matter.
Before following an installation command, I will check the account and terminal it expects. On Windows, Ubuntu needs to belong to my work account. An administrator terminal can run as a different user.
My first tools will be an editor, Git, the software needed to run the project, and one AI assistant. That might mean Node.js for a JavaScript website or Python with its own project package environment.
My next step is a disposable project that runs successfully in the chosen workspace. I will use the current installation instructions for my computer and record the versions I install.