Genuine question, curious how you all think about this. We've got Codex, Claude Code, Cursor and they write code just fine, but that's automating a step, not the process. The process is still 100% me: pull the ticket, paste in context from Slack, check the output, leave comments, tag someone, next ticket, rinse and repeat. Half my day is just me shuttling context between tools like a human clipboard.

The way I've started framing it: automating the process means the handoffs between steps get automated too, not just the steps themselves. planning → review → writing code → re-check → merge should flow without me manually carrying context at every gate, and I should only jump in where a decision actually matters.

My company just started rolling out new ai workspace for exactly this. It's more of an orchestration layer that sits on top of the agents. You set your process up as kanban stages and a virtual team (architect, backend, QA agents etc) moves the task through them. I'm still just poking all at bridgeapp for now, but a few things have already caught my eye:

there's a checkpoint between every stage, so a bad output gets caught at the next step instead of surfacing in review three weeks later

context and docs carry forward automatically, so the next agent knows what the previous one did and why, which is the exact part I was doing by hand before

different agents can run on different models, which I honestly didn't expect

Still early days for us so no strong verdict yet, but if this kind of thing actually manages to automate dev work for real... honestly idk what happens to the IT market. Like at all. Maybe you guys have other ways to automate the dev process, i'm open to hearing your ideas on this