It is starting to feel strange when the work stops as I sleep

It is starting to feel strange when the work stops as I sleep.

There is an old line about wealth that says you are not really rich unless your money earns while you are asleep. I dislike most of the atmosphere around that sentence: the status anxiety, the financialized self-help, the faint smell of someone trying to sell you a course. But after stripping all that away, there is a useful shape underneath it. Certain systems start to feel different once they can keep doing useful things after your attention has left the room.

Agents are beginning to rhyme with that feeling. If every useful action requires me to sit there, approve the next step, paste the next command, watch the next test run, and decide the next branch, then the agent still feels close to an interface: powerful, useful, often impressive, but tethered to my continuous presence. The stranger feeling begins when the agent can accept a bounded job, carry context forward, make reversible progress, validate its own work, and come back with evidence.

Sleep is a good test because it removes the comforting fiction of continuous supervision. While I am awake, even a fragile agent can feel autonomous because I am quietly holding the whole system together: noticing when it drifts, supplying missing context, approving tool calls, restarting failed processes, interpreting ambiguous errors. Overnight work exposes whether the harness actually contains the job. Does the agent have the repository, credentials, budget, permissions, tests, memory, stopping rules, escalation path, and review surface it needs? Or does it only look capable while a human is nearby to catch every dropped thread?

The point is not that I should be working while asleep. It is almost the opposite. The point is to separate progress from vigilance. A good agentic setup should let me define the shape of acceptable work, go away, and return to something inspectable: a branch, a failing test with diagnosis, a draft, a queue of proposals, a narrowed question with the relevant context already gathered. Morning should not contain magic. It should contain receipts.

Attended agents are already a core part of how I work, and I do not want to diminish that mode. Sitting with an agent, steering it, correcting it, and using it as an extension of attention is genuinely useful. But there is another mode beginning to come into view. We already accept background competence from CI, cron, monitors, queues, and deployment systems. Agents seem likely to join that family, but with more judgment and therefore a much stricter need for harness. An agent without overnight competence can still be excellent. It just belongs to a different rhythm of work.

I do not think this is a definition yet. It is more of a taste forming in real time: once an agent can plausibly keep working while I sleep, it becomes harder not to expect that from the category.