Not everyone needs Claude in the cloud. I checked why I do.

Who doesn't need it

If you work at one desk, on one project, and nobody is waiting on you, an always-on Claude buys you nothing. Same if you already have a computer that never sleeps, a Mac mini in the living room or a desktop you leave on. T3 Code runs on that machine exactly as it runs on a server, with no cloud at all. Several people on the last post run it that way and they are right to.

The cloud server only earns its EUR 11.28 a month when the machine you carry is the one that sleeps.

What the log says

From the evening I moved to T3 (3 November) to the afternoon of 6 November, I typed 229 messages to Claude. 25 came from the phone, about one in nine. That is not much. The timing is the point:

• Wednesday 16:46 to 17:27, away from the computer. "Send it to the client and my partner, turn it into a spec, then tickets, then start building. We'll adjust to their answers." By 17:20 they had answered. At 17:27: "the client is good enough, he's the main stakeholder, follow his lead." A full planning round with a client in 41 minutes, five messages from the phone.
• 22:18, at night. "Check if there's anything new and unhandled in the client's WhatsApp group."
• 08:27, from the phone again. "Fix it." "Publish it, I'll look again." "We need a KISS interface that is easy to drill down into when needed."
• 10:48, another client. Someone there noticed that two calendars in their app look different. I dictated it into the phone and the fix started.

Read the messages, not the counts. "Go." "Fix it." "Publish it." "Follow his lead." None of them is code. The agent writes the code; what it needs from me is a decision, a direction or a yes. Those fit on a phone. The laptop is still where I review, test and do the long thinking; that is the other eight messages out of nine.

So, the business value

• Clients get an answer while I'm moving. Before, "I'll check when I'm at the computer" quietly became two days. Now a client's message turns into work in minutes, from wherever I am.
• Development doesn't wait for the desk. A spec round, a fix, a publish: each starts when the decision is made, not when I sit down.
• The scarce resource is me, available. For a freelancer with a few clients on WhatsApp, compute is cheap. Being reachable is what they notice.

Check yours

If you run T3 Code, this counts where your messages came from. Run it on the machine running the T3 server:

sqlite3 -readonly ~/.t3/userdata/statev2.sqlite \
  "select json_extract(payload_json,'$.creationSource') as source, count(*)
   from orchestration_v2_projection_messages
   where role='user' group by source;"

In my log the phone app shows up as mobile and my Mac as web. Compare those two; the other sources (provider, server, mcp) are not what I typed on a device (provider and server alone hold hundreds of rows from three days), so I leave them out. T3 is alpha (0.1.x), so the table name may change between versions. If the phone share is near zero, you are probably one of the people who doesn't need the cloud part.

The earlier posts

• Claude Desktop is dead. My laptop is a server now. (the T3 Code setup)
• My Claude lives in a shed now (the EUR 11.28 server)
• Keeping claude rc alive on a Mac