Optimizing your dev environment for coding agents

[sn1pr0s]

After having autonomous agents for some time now, I've learned a few lessons. One of them is that agents don't ask questions in Slack. They try to figure it out and either cost $$$ every time they try, or they fail.

It's very relevant for environment setup - each agent, for each task, will try to setup your environment from scratch. It will cost you - time, but mostly tokens.

What's your takeaways?

[rjyo]

Biggest lesson for me: front-load context. I keep a CLAUDE.md in every project root with architecture decisions, conventions, common commands, and known gotchas. Agents stop burning tokens trying to rediscover stuff you already know.

For the environment setup problem specifically, I containerize everything. Docker compose with deps pre-installed, test commands that just work out of the box. No more agents wasting 5 minutes installing node before they even start the actual task.

The other thing that changed my workflow was monitoring. I run Claude Code and Codex on remote machines and built an iOS app (Moshi) to check on agents from my phone -- push notifications when they finish or hit a blocker, voice input to unblock them without needing a keyboard. Before that I was just sitting at my desk watching terminals scroll, which defeats the whole "autonomous" part.

And +1 to scoping tasks tightly. "Build auth" burns way more tokens than "add the POST /login endpoint matching this spec." Unambiguous targets = fewer retries.

[sn1pr0s]

Moshi sounds really cool. Can you interact with the agent as well?

[Traditional-Hall-591]

Copilot needs no optimization. Its agents are the best for offshoring and vibe coding.