The Remote Engineer's Toolkit for 2026

Every "remote developer toolkit" article I've read is the same: buy a standing desk, get a good monitor, use Slack. That advice made sense in 2020. In 2026, the toolkit looks completely different - especially if you're doing AI-first development. Here's what I actually use, day to day, with honest opinions on all of it.

Terminal Setup: The Foundation

Your terminal is where you live. Make it fast, readable, and pleasant to use. Here's my stack:

Ghostty

I switched to Ghostty six months ago and I'm not going back. It's GPU-accelerated, genuinely fast, and feels native on macOS in a way that Alacritty and Kitty don't. The configuration is simple - a single config file, no YAML nesting hell. I run a Catppuccin Mocha theme with Monaspace Neon font and a subtle bloom shader that makes the terminal feel alive without being distracting.

Key bindings I can't live without: Cmd+D to split right, Cmd+Shift+D to split down, and Cmd+` for a global quake-style dropdown terminal. That last one means I can summon a terminal from anywhere with a single keystroke.

Starship prompt

Starship gives you a fast, informative prompt that shows git branch, language versions, and cloud context without any lag. I use a Catppuccin colour palette so it matches the terminal theme. It's written in Rust, so it loads instantly - none of the lag you get with oh-my-zsh themes.

Modern CLI replacements

The standard Unix tools are fine, but modern replacements are genuinely better:

• eza replaces ls - tree views, git status integration, icons, colour-coded by file type
• bat replaces cat - syntax highlighting, line numbers, git diff integration
• delta replaces the default git diff - side-by-side view, syntax highlighting, line numbers
• zoxide replaces cd - learns your most-used directories, z project jumps you straight there regardless of where you are
• zsh-syntax-highlighting - colours your commands as you type them, red for invalid commands, green for valid

These aren't just cosmetic. When you're reviewing AI-generated diffs multiple times a day, having readable, well-formatted output saves real cognitive load.

AI Tools: The Multiplier

Claude Code with Team Lead Mode

This is the centrepiece of my workflow. Claude Code acts as a team lead - it creates teams, assigns tasks, spawns background agents, and coordinates their work. I've written extensively about this in other posts, so I'll keep it brief: it turns one developer into a development team.

The key configurations that make it work remotely:

• Model routing - Opus for complex work, Sonnet for verification, Haiku for trivial checks. This keeps things fast and cost-efficient.
• Hook-driven guardrails - 11 hooks that prevent agents from committing secrets, skipping formatting, or modifying generated files. Essential when agents run unsupervised while you're away from your laptop.
• Voice announcements - macOS say with the Zoe Premium voice announces when agents finish or need attention. Ambient awareness without constant screen-watching.

Git worktrees for isolation

Each feature gets its own worktree. This means agents working on one feature can't affect another, and if something goes wrong, the blast radius is contained. It also means you can run dev servers for different features on different ports simultaneously - useful when you're comparing implementations.

One gotcha: .env files are gitignored, so they don't exist in new worktrees. I symlink them from the main worktree. Agents with worktree isolation handle this automatically.

Hardware: Less Than You Think

Here's where I diverge from most "toolkit" articles. You don't need a standing desk, a 4K monitor, and a mechanical keyboard to do serious engineering work. Here's what I actually travel with:

• MacBook Pro (M-series) - the machine itself. Enough power to run everything locally, enough battery to survive a transatlantic flight. The screen is good enough that I don't miss an external monitor.
• Google Pixel Buds Pro 2 - noise cancelling for cafes, trains, and co-working spaces. The ANC is outstanding for the size, and the transparency mode is natural enough to hold a conversation without removing them.
• Anker portable charger - the MacBook's battery is great, but a long day of agent-heavy work with multiple terminals can drain it. A compact USB-C power bank extends the day.
• Phone with a good data plan - your backup internet. Always. Cafe wifi will let you down at the worst moment. A phone hotspot with 5G is more reliable than most public wifi.

That's it. Four things. I've seen setups with portable monitors, external keyboards, laptop stands, webcam lights, and cable organisers. If that works for you, great. But I've found that the less I carry, the more likely I am to actually go somewhere interesting - and the AI-first workflow means I don't need the ergonomic setup of someone coding for 8 hours straight.

Connectivity: The Real Challenge

Spotty wifi is the number one challenge of working remotely. Here's how I deal with it:

• Batch your online work. Spawn agents and push commits when you have good connectivity. Review code and plan work offline.
• Short sessions. A 30-minute focused session needs much less reliable internet than an 8-hour marathon. The AI-first workflow naturally encourages shorter sessions.
• Offline-capable workflows. Git is inherently offline-capable. Write your prompts and plan your tasks in a text file. Connect, execute, disconnect.
• Know your backup. Before sitting down to work, check that your phone hotspot works in the current location. Nothing worse than finding out there's no signal when you're mid-deploy.

Communication: Async-First

Remote work lives and dies on communication. When you're not in the same timezone or even the same country as your team, async communication isn't optional - it's primary.

• PR descriptions that tell a story. Not "fixed the bug" but "the discount calculation was using the old formula from before the March pricing update, which caused enterprise customers to see incorrect totals on the checkout page." Future-you and your teammates will thank you.
• Commit messages with context. The what is in the diff. The commit message should explain the why.
• Documentation as a habit, not a chore. When you figure something out - how a tricky module works, why a decision was made, what the workaround is for a known issue - write it down immediately. If it's not written down, it's lost the moment you close your laptop.
• Overcommunicate, then dial back. When you start working remotely with a new team, share more context than you think is necessary. You'll naturally find the right level, but starting with too much is better than too little.

Environment: Dark Mode Everything

This might sound trivial, but consistency matters when you're working from different locations every week:

• Consistent dotfiles. My terminal config, git config, shell aliases, and tool configurations live in a dotfiles repo. New machine? Clone the repo, run the setup script, and I'm working in 10 minutes.
• Dark mode everywhere. Terminal, browser, GitHub, Slack, VS Code (when I use it). Not just preference - it's practical. Dark mode is easier on the eyes in dim cafes, on planes, and in hotel rooms. And when your screen is visible to people nearby, dark mode is less attention-grabbing.
• Quick setup scripts. I have a script that installs Homebrew, all my CLI tools, Ghostty, and configures everything from the dotfiles repo. It runs in about 5 minutes. I've used it three times this year - once for a new machine and twice for fresh OS installs.

What You Actually Need vs What You Think You Need

The honest truth: you need less than you think. The essentials are:

1. A good laptop
2. Noise-cancelling headphones
3. A phone with hotspot capability
4. A well-configured terminal
5. An AI workflow that lets you work in short bursts

Everything else is nice-to-have. The external monitor, the standing desk, the mechanical keyboard - these are optimisations for a workflow where you're at a desk for 8 hours. If your workflow is 90 minutes of focused sessions spread across the day, you don't need the ergonomic investment.

The biggest upgrade to my remote work setup in the past year wasn't hardware. It was Claude Code's Team Lead Mode. It changed my working pattern from "8 hours at a desk" to "short bursts of direction-setting between living my life." No piece of hardware can do that.

Invest in your software setup. Your hardware just needs to be good enough to run it.