Dev Toolbox for Beginners: Editor, Git, Terminal, Toolbx
A beginner's developer toolbox needs five things: a code editor, a terminal, Git, a package manager, and a debugger. Install them in that order, on your own machine first. Once that works, you can move the same setup into a container (Toolbx on Linux, or a dev container) or a cloud "developer box" such as GitHub Codespaces.
This guide gives the exact install commands for macOS, Windows and Linux as of October 2026, explains the Linux toolbox command, and compares the ways to get a ready-made dev environment. Skip anything you already have.
The minimum dev toolbox
| Tool | What it does | Good default |
|---|---|---|
| Code editor | Write and navigate code | VS Code (free) or a JetBrains IDE |
| Terminal | Run commands, scripts, Git | Terminal (macOS), Windows Terminal + WSL, your distro's terminal |
| Version control | Track changes, collaborate | Git + a GitHub or GitLab account |
| Package manager | Install tools and libraries | Homebrew, winget, apt/dnf; npm/pip for language packages |
| Debugger | Pause code and inspect state | Browser DevTools, your editor's debugger |
Everything here is free. You don't need paid tools to learn. When you want to compare options later, DevHunt keeps lists of IDEs and editors and CLI tools.
Step 1: Pick an editor
Pick one and stick with it for a few months. Switching editors early is a common way to lose time.
- VS Code is free, runs on all three platforms, and has extensions for nearly every language. It also has a built-in terminal, Git panel and debugger.
- JetBrains IDEs (IntelliJ IDEA, PyCharm, WebStorm) do more out of the box for one language. Some have free editions or free licenses for students.
- Vim or Neovim are worth learning eventually, because you'll meet them on servers. They aren't a good first editor.
Learn three shortcuts on day one: open a file by name, search across the project, and open the command palette (Ctrl+Shift+P or Cmd+Shift+P in VS Code).
Step 2: Set up a terminal
- macOS: the built-in Terminal app is fine. The default shell is zsh.
- Windows: install Windows Terminal, then install the Windows Subsystem for Linux so you get a real Linux shell. In an administrator PowerShell, run:
wsl --install
This installs WSL with Ubuntu by default (see Microsoft's WSL install guide). Most tutorials assume a Unix-like shell, so working inside WSL saves you a lot of translation.
- Linux: use your distro's terminal.
The commands you'll use every day: pwd, ls, cd, mkdir, cp, mv, rm, cat, grep, and man <command> (or <command> --help) to read the manual.
Step 3: Install a package manager
A system package manager installs and updates your tools with one command, so you don't download installers by hand.
macOS: Homebrew. The install command from brew.sh:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Windows: winget. It ships with current Windows 10 and 11 as part of App Installer. See Microsoft's winget docs.
winget install --id Git.Git -e
winget install --id Microsoft.VisualStudioCode -e
Linux: your distro already has one: apt on Debian and Ubuntu, dnf on Fedora, pacman on Arch.
Language package managers sit on top: npm comes with Node.js, pip with Python, cargo with Rust. Install a language runtime through a version manager (such as nvm for Node or pyenv for Python) when you need more than one version.
Step 4: Install and configure Git
Install Git with your package manager (brew install git, the winget command above, or sudo apt install git), then tell it who you are:
git config --global user.name "Your Name"
git config --global user.email "you@example.com"
git config --global init.defaultBranch main
Then learn the core loop. The Pro Git book is free and official:
git init # start tracking a folder
git status # what changed?
git add . # stage changes
git commit -m "Add login form"
git log --oneline # history
git switch -c feature-x # new branch
Create a GitHub account and push a project. Commit small, commit often, and write messages that say what changed.
Step 5: Learn to debug
Debugging with print statements works, but a real debugger is faster once you know it:
- Browser DevTools (F12 in Chrome, Edge and Firefox): inspect HTML and CSS, watch network requests, set breakpoints in JavaScript.
- VS Code's debugger: click left of a line number to set a breakpoint, press F5, then step through code and inspect variables. See Debugging in VS Code.
- Read the error. The first line of a stack trace usually names the file and line. Search for the exact error message in quotes.
Toolbx: the toolbox command on Linux
If you're on Linux, Toolbx (the toolbox command) gives you a disposable, mutable Linux environment in a container. You can install compilers and libraries there with the normal package manager without touching your host system. It's built on Podman and comes preinstalled on Fedora Workstation and Fedora Silverblue. On other distros you install the toolbox or podman-toolbox package (install docs):
sudo apt install podman-toolbox # Ubuntu
sudo pacman -S toolbox # Arch
The core commands, from the toolbox man page:
toolbox create # container matching your host, e.g. fedora-toolbox-42
toolbox enter # open a shell inside it
toolbox list # show containers and images
toolbox run gcc --version # run one command inside it
toolbox rm fedora-toolbox-42 # delete the container
To pick a different distro, pass --distro and --release, for example toolbox create --distro ubuntu --release 22.04. The supported distros page lists Arch, Fedora, RHEL and Ubuntu.
What makes it useful for development: your home directory, network, SSH agent, display (Wayland and X11) and D-Bus are shared with the container, so your editor and dotfiles just work. The flip side is that Toolbx is not a security sandbox. The project says it makes no security promises beyond your normal command line.
Toolbx is only for Linux hosts. On macOS and Windows, the equivalent idea is a dev container.
Developer box options: local, container or cloud
"Developer box" usually means a ready-to-code machine. There are four practical ways to get one:
| Option | Where it runs | Cost (as of October 2026) | Best for |
|---|---|---|---|
| Local install (steps 1-5) | Your machine | Free | Learning, most daily work |
| Toolbx | Container on your Linux host | Free | Keeping your Linux host clean |
Dev container (.devcontainer/devcontainer.json) |
Docker locally, or in Codespaces | Free locally | Reproducible setup per project |
| GitHub Codespaces | GitHub's cloud | Free personal accounts: 120 hours of compute and 15 GB storage per month | Working from any device, onboarding |
A dev container is a project-level config file that tells VS Code which container to build. The smallest useful one, from the VS Code docs:
{
"image": "mcr.microsoft.com/devcontainers/go:1"
}
Open the project and run Dev Containers: Reopen in Container from the Command Palette. The same file works in Codespaces.
Codespaces' free hours are counted with a machine multiplier (GitHub billing docs). A 2-core machine uses 2 included hours per real hour, so the free 120 hours is about 60 hours on the smallest machine.
Two other things people mean by "developer box":
- Microsoft Dev Box, Azure's cloud dev workstations. It stopped accepting new customers on November 1, 2025, and its features are moving into Windows 365 (Microsoft's announcement). Existing customers can keep using it.
- Box's developer platform (APIs and SDKs for the Box file-storage service) lives at developer.box.com. That's an API, not a dev environment.
A first-week plan
- Day 1: install the editor, terminal and package manager.
- Day 2: install Git, configure it, create a GitHub account.
- Day 3: install one language runtime and build a tiny project (a CLI script or a static page).
- Day 4: put it in Git, push it to GitHub.
- Day 5: set a breakpoint and step through your code once.
After that, add tools only when a real task needs them. A beginner with five tools they know well gets further than one with thirty they don't. For more on choosing tools as you grow, see types of software development tools, with examples. If you want to try AI coding assistants once the basics click, start with the vibe coding tools list.
FAQ
What is a dev toolbox?
It's the set of tools you use to write, run, track and debug code: an editor, a terminal, Git, a package manager and a debugger. On Linux, "toolbox" can also mean Toolbx, the toolbox command that creates development containers.
What is the toolbox command in Linux?
toolbox is the CLI for Toolbx, which creates and enters Podman containers that share your home directory and user session. toolbox create makes a container, toolbox enter opens a shell in it, and toolbox rm deletes it. It's preinstalled on Fedora Workstation and Silverblue.
Do I need Docker to use Toolbx?
No. Toolbx uses Podman, which it installs as a dependency. Dev containers in VS Code do need a container engine such as Docker locally, or you can run them in GitHub Codespaces.
Is GitHub Codespaces free?
Personal GitHub Free accounts get 120 hours of compute and 15 GB of storage each month (as of October 2026). Usage is multiplied by machine size, so on a 2-core machine that's about 60 hours.
Should a beginner use a cloud developer box?
Learn on your own machine first. You need to understand your terminal and file system anyway. Cloud environments like Codespaces are useful when your computer is too slow, or when a project ships a dev container and you want to start without installing anything.