// posts/the-workflow-shift-that-changed-how-i-build-software.md

I've been coding with AI for a while now, but this workflow shift actually changed how I think about development. I used to open an IDE or a CLI tool and pull up a ticket. It works. But recently I switched to Codex (https://chatgpt.com/codex) a chat-first interface where the entire left panel is just my active projects. Here's what makes it different: I'm usually juggling 3-4 repos at once. I prompt in one project, and while the agent processes, I switch to another and keep working. No tmux sessions. No tracking which terminal belongs to which repo. No mental overhead of "wait, which window was that build running in?" ⚡ All projects visible in one sidebar ⚡ Queue multiple prompts across repos ⚡ Run, test, view diffs, and commit directly from the interface The speed caught me off guard. I'm getting most of my work done this way now, not because the models got better (though they did), but because the UX finally makes sense for parallel workflows. I think 2026 is the year these UI-first AI coding tools go mainstream. CLI tools had their moment and they're still great for certain workflows, but managing terminal history and multiple tabs on a laptop starts to feel brittle. The real shift isn't the AI. It's learning when to take control and when to let it run. Many of us have gotten decent at prompting. We know how much context to give. We know which parts need human judgment. That's when the workflow becomes effortless. One reality check: this workflow amplifies both productivity and mistakes. You need stronger discipline around reviewing diffs because you're shipping faster than your brain can context-switch. The mental model shift is worth it-just don't skip the review step. #AIEngineering #SoftwareEngineering #DevTooling #AIWorkflows #DeveloperExperience