THE testimony arrived on the r/ChatGPT forum in April of this year, posted without fanfare by a software developer whose working life has achieved a peculiar new structure. He builds websites and applications using artificial intelligence coding tools—Claude Code and Codex principally, with Cursor set aside as operating under a different usage model. He did not write to complain. He wrote to ask a question. The question was whether this was happening to everyone.
What is happening to him is this: the rate limits imposed by his tools' subscription tiers now govern his circadian rhythm. He codes until the machine informs him it has exhausted its willingness to continue. He then eats lunch. Or he performs the duties of his full-time salaried position. These activities are described not as primary occupations but as interstitial ones—filler poured into the gaps between productive sessions with the machine. At night, he works until the session limits are reached again, and then he goes to bed. Not because he is tired. Because the tool is.
Usage-tier pricing, as practiced by Anthropic, OpenAI, and their competitors, operates on a model that will be familiar to anyone who has studied the rate structures of electrical utilities. A subscriber purchases access at a given tier. That tier entitles him to a certain volume of computation per unit of time—tokens per hour, requests per session, and some proprietary measure of intensity that the provider calibrates and adjusts without notice. When the allocation is consumed, the tool becomes unavailable. It returns to service when the cycle resets. The reset intervals are not published with the regularity of a bus schedule, though they function as one.
What the pricing engineers have produced, perhaps without intending to, is a shift system. The developer in question now works shifts. His shift begins when the rate limit resets and ends when it is reached. The interval between shifts is not leisure; it is the period during which he performs his other, salaried employment and attends to biological maintenance. The tools marketed as productivity multipliers—and priced accordingly, at rates between twenty and two hundred dollars per month depending on tier and provider—have re-created the factory whistle. The whistle simply blows at irregular hours and is audible only to the individual worker.
This is not, strictly speaking, employment. No contract exists between the developer and the provider of his artificial intelligence tools that could be described as an employment relationship. He is a customer. The terms of service are explicit on this point. And yet the operational reality is that his productive hours, his meal times, and his sleep schedule are determined not by his own judgment or by the demands of his nominal employer but by the capacity allocation decisions of a company that does not know his name and has no opinion about when he should eat.
The condition has historical antecedents, though none of them are precise. Piecework laborers in the nineteenth-century garment trade were governed by the availability of material from the cutting room; when no pieces were available, they waited without pay. Taxi drivers on the medallion system work when demand exists and idle when it does not, their hours set by the city's rhythms rather than a dispatcher's command. But in both cases the constraint was understood to be a constraint. The garment worker did not describe the cutting room's schedule as his own productivity system.
The developer's testimony is notable for the absence of grievance. He does not describe his situation as intolerable. He describes it as a schedule. The machine sets his hours; he keeps them. The question he poses—"Is this really what's happening to all of us developers?"—carries the particular tone of a man who suspects he has identified a structural condition but is not yet certain whether it is a personal eccentricity or a collective one. He is polling. The responses in the forum thread suggest it is not only him.
The providers of these tools have, through ordinary commercial decisions about pricing tiers and rate limits, acquired a form of authority over their subscribers' daily lives that is functionally indistinguishable from the authority of an employer over a shift worker. They exercise this authority without assuming any of the corresponding obligations—no overtime pay, no mandated rest periods, and no occupational health considerations. The relationship is entirely contractual, entirely voluntary, and entirely one-directional. The developer may cancel his subscription at any time. He does not cancel his subscription.
It is worth noting, without editorial comment, that the developer performs his salaried employment—the work for which he is compensated, for which benefits are provided, for which presumably some entity has filed the relevant tax documents—in the intervals when his unpaid tools are resting. The job is what he does while waiting.