Pinned Tweet
I run several Claude Code sessions a day across client repos, and nothing recorded them. My own timers I often forgot.
So I'm building Tock, a Mac menu bar time tracker: my hours and Claude Code's, kept apart, records on my Mac.
Not out yet.
“There is too much text.” That was one tester’s first impression of Tock, a Mac menu bar time tracker that also records Claude Code. Four testers have the beta, which started Monday. I’m cutting onboarding to three short screens.
What did your first tester actually say?
2
47
Apple’s Developer Program enrolment, as a company: 27 days. Started 13 Oct, approved 9 Nov.
Before you start you need a D-U-N-S number, a public website on the company’s domain with real content and an email address on that domain. Apple rejects placeholder pages.
23 days in, Apple emailed asking for the company’s documents. I sent them the same day, and the approval came four days later. Until then there was nothing to do but wait. On 2 Nov there was no case number and the status page said “Your enrollment is being processed”.
What you can’t do without it: a Developer ID certificate, notarization or iCloud. A Personal Team can’t use them, so an app sold outside the App Store can’t be signed or notarized for anyone else’s Mac.
What I did while waiting was everything that needs no certificate: privacy policy, terms and refund policy published, the update loop tested on my own Mac, work on sync, test coverage from 94.9% to 97.3%.
Since the approval: the first signed and notarized build, bug fixes and small quality-of-life tweaks. Now working on the next big one: one record of your time across several Macs and Linux machines.
1
1
110
D-U-N-S: Apple has a free lookup and request flow for developers, so you don’t need to pay D&B for one. Start here: developer.apple.com/help/acc…
24
I'm looking for 5 beta testers for Tock, the Mac time tracker for clients and Claude Code.
You need a Mac on macOS 14 or later and two weeks, 16 to 27 November. You get a free lifetime licence for your time.
Reply here or send me a DM.
Tock shows you the time Claude worked unattended. If Claude is still working 5 minutes after your last message, the rest is drawn fainter, so you can see at a glance where it worked with you and where it worked alone.
Nothing is thrown away. It just makes it easier to see when you worked together and when Claude worked alone.
1
35
Claude Code made subagent status updates ~99% cheaper: no more re-reading the whole conversation. Tock fixed a similar waste on 19 Oct.
It used to ask Claude Code to name its work. One headless 100-word answer: 2–3 turns, 6.0–10.1 s with the ask; 1 turn, 2.6–2.9 s without. About 280 tokens a session, for a name.
Then I read 191 of my own Claude Code transcripts from ten days. Interactive sessions already name themselves: 107 of 128 had a title Claude Code wrote during the first turn. /rename writes one too. The title was already there to be read.
So now Tock asks nothing: 0 tokens, and its hook adds about 20 ms before each message. The "to-do" is named from your first message, with the git branch in front, then from Claude Code's own title.
Prefer the old way? "Ask the agent to name its work" is a switch in Settings › Agents.

ALT Bar chart. claude -p, one 100-word answer, Sonnet. Before 19 Oct, asked to name its work: 6.0 to 10.1 seconds, 2 to 3 turns, about 280 tokens a session. Today, asks nothing: 2.6 to 2.9 seconds, 1 turn, 0 tokens. API time, headless runs. Both also wait 20 to 23 ms for Tock’s hook before each message.
hot take: you don't need a software factory, and i don't love the term. it's just marketing
all you need is good software engineering and investing your tokens in the right places. the more deterministic the better (and token efficient)
Basit Anwer retweeted
I've been training the most natural realtime Urdu voice model at home 👇
Most tools I've tried haven't felt very natural in Urdu. I wanted something that sounds closer to how we actually speak Urdu.








