I've been running Claude Code, Cursor, and Codex pretty heavily for the last few months and I keep hitting the same loop:

1. Start a task in one agent

2. Switch to something else (Slack, Twitter, another terminal)

Two months ago I asked here how people stay aware of what their agents are doing, and @getosmo replied with something that has been quietly rearranging my roadmap since.

I had been treating "can you undo it" as the line for when an agent should stop and ask. He took that apart. Irreversibility over-fires and under-fires, he said. It over-fires on things that cannot be undone but that nobody cares about, like the agent writing a log line. It under-fires on the ones that really hurt: a mass email to 50k users, or a migration you can only roll back after downtime. "Reversible on paper, ruinous in practice."

Open the terminal where your agent is running. Do it now, before you read the rest.

Is something sitting there waiting for you? How long has it been there?

I had Claude Code running behind a notes window. It reached a permission prompt and sat there while I kept working. I was on the same Mac the whole time.

That felt worse than missing a finished task. I was not away. The terminal was simply not where my attention was.

one of the shops we support does photo prints. someone asked if they also print diplomas. they do not. the assistant gave a vague answer, the customer asked again more directly, and the second time it said yes. they sent the file to print.

we sorted it out and nobody lost money, but the second answer is the part i keep thinking about. the first one was hedged. it only became a yes after the person pushed. so it did not really invent a product, it agreed with a confident customer.

I run Claude Code, Cursor, and Codex most of the day, and I keep flip-flopping between two setups that both feel wrong.

Setup 1, babysit: I watch every command and approve everything myself. Nothing slips past me, but I'm stuck at the terminal and the whole point of running an agent is gone. I might as well be typing it myself.

I ve been thinking about this a lot while building Verzii.

As AI agents become more capable, we re giving them more responsibility to plan, execute, make decisions, and work in the background.

But there s an interesting problem:

How do you know what your agent is actually doing when you re not watching it?