Use Codex and Claude macOS apps as my primary engineering environment
Default to agent workbenches for engineering work, with Codex first when browser-backed inspection matters and VS Code reserved for precise file edits.
Context
My day-to-day software work has moved from an editor-centered workflow into agent desktop apps that hold the repo, shell, browser, instructions, and review loop.
Why
Most engineering work now benefits more from an agentic workbench that can coordinate repository context, terminal commands, browser inspection, edits, and validation than from direct manipulation inside a traditional editor.
Reconsider if
I would reconsider if agent desktop apps became less reliable for repository work, if their browser and shell loops stopped feeling integrated, or if VS Code regained a clear advantage for the majority of engineering tasks.
Codex and Claude’s macOS apps are now my primary engineering environment.
VS Code is still part of the loop, but mostly for direct file-related tasks: quick manual inspection, targeted edits, or work where I specifically want an editor surface. The center of gravity has shifted elsewhere.
For most engineering work, I now prefer to start in Codex or Claude. Codex is the default when the task benefits from the immersive browser view, because it makes implementation, local verification, and UI inspection feel like one continuous workspace rather than separate tools I have to manually coordinate. Claude remains useful as another high-quality agentic engineering surface, especially when I want a different model’s judgment or interaction style.
The decision is less about brand loyalty than workflow shape. The thing I want to inhabit is no longer just a file tree plus terminal. It is the loop that moves from intent to context gathering, patch, test, browser inspection, correction, and handoff.