I've heard the same concern from multiple fellow engineers recently. It also often comes with a fear that they'll be doing only "boring PRs review" in the future, or even worse - that their AI agents will be just talking to other engineers AI agents without involving humans :/

I believe it's really important to stop reading every line of code during the PR review and go one level higher. Work on the guardrails, security, creative parts of the architecture, challenge architectural decisions of your AI setup and learn. It's also often related to the lack of trust to the code generated by your setup, if you don't believe it then you spend a lot of time finding issues without actually improving anything.

Once you built a trust in what your AI generates, then you can skip many boring parts and focus on more creative things (or whatever you like more).

Btw if you don't like looking at a terminal window half a day then create a better interface in your setup - it can be better storytelling, diagrams, visuals, charts, whatever you like to make it feel better :)

Personally I'm more into diagrams and flows, so I try to turn every PR review into higher level flow analysis where I can predict what might be wrong, architecture flaws and so on instead of reading every line of code.