Short version · Full version
11:54 — 9 November 2026
Claude Code and
Cowork: six months in brief
May to November 2026. The short, bullet-point version of the full
overview.
The one-minute version
- You’ve been busy. 3,191 messages in Code and 597 in
Cowork. You worked on 156 of the 193 days since 1 May.
- You build well. Odeon, the ASDA tick page,
todo-php, the WhatsApp alerts and many hardware fixes all work, and you
use them.
- Finishing is the soft spot. “Done” projects keep
growing. Small real-life jobs sit for months.
- What runs itself lasts. Hooks, the session-start
todo block, the Odeon scraper and the WhatsApp alerts survive. Anything
you have to remember to start has faded.
- Most of the anger came from four delivery failures:
where is it, why am I waiting, too much text, and you didn’t check.
- Your nights are getting later. Messages after 23:00
went from about 10 a month (May to July) to 120 in October.
The numbers
- Busiest months: June (608 messages) and October
(581). The quietest was September (389).
- Peak hours: 13:00 to 16:00, with a second wind at
19:00 to 20:00. Almost nothing between 03:00 and 08:00.
- Tuesday is your quiet day: 294 messages, against
670 to 900 on every other day.
- Odeon took the most effort: about 12,000 Claude
turns and 164 git commits. Hardware was the steadiest thread, there
every month.
Project by project
- Odeon. Live at v9 and good on phone and PC. It did
its main job by June (“finally there”, 12 Jun). Four picks remain
(Labels, Films, Gantt Bars, Samples), then it needs a freeze, or it
becomes a forever-project.
- OT48. The site is built and secured, but there are
zero outside customers. It’s waiting on Oregon, where the cousin is
unwell, not on code.
- ASDA. About 38 orders and 201 items logged, plus
the tick page and a price tracker (from 23 Oct). It has worked best
since you took the logic back on 5 Sep.
- todo-php. Your most-used tool, and the only one of
five todo systems still alive. It’s also the one you over-build: the
limits you set on 8 Jul didn’t hold.
- Morning news. It grew until it became a chore. You
cancelled it on 8 Nov (the task is disabled, not deleted), and that was
a good call.
- Hardware. Big wins: the second NVMe drive, the GPU
blank-screen fix (493 events down to zero), the slow shutdown and the
mystery wake-ups. Still open: monitor audio, the Killer Wi-Fi errors and
the slow H: drive.
- Phone and comms. The notification noises are cured,
the tabs were cleared on 5 Nov, and WhatsApp alerts have worked since 11
Oct (52 sent). The cleanest success of the six months.
- Cowork. Mail triage found a forgotten £150 energy
card. The Thames Water charts and letters are done, but the cause is
still unknown. Code is where you build; Cowork grinds through messy
one-off jobs.
- The quiet ones. The Money plan (untouched since 9
Jun), ActivityLogger (since 13 Jul, with four decisions waiting), the
bus app, aftertheappointment, the Prime spec and TV films are all parked
mid-flight.
What has worked
- A small step, then you test. The Gantt overlap fix
got “100% PERFECT. Pls mark as final” (25 Sep).
- Options side by side. You decide fast when you can
see three to seven versions.
- Concrete problems with evidence. Hardware goes well
because there are logs and event IDs.
- You hold the logic, Claude does the legwork. ASDA
after 5 Sep is the proof.
- Small things that are finished. WhatsApp alerts,
/tellme and the tab clean-up each do one job.
- Things that run themselves. The session-start
block, the 25-minute reminder and the scraper.
- Rolling sessions as your outside memory. In
Hardware central and the Cowork mail session, “update pls” picks the
thread straight back up.
- Saying stop. Killing
/away (17 Jun)
and cancelling the news (8 Nov).
What hasn’t worked
- Overnight “be creative” builds. All six Odeon
prototypes were rejected (22 Jun).
- Claude guessing about your world. The ASDA
demotions, Agna’s location, and a film on the wrong day.
- Claude driving the desktop or phone. The
/away chaos, the Tasker stalls, and test clicks that
unticked two of your real films.
- Big parallel agent runs. Six Opus agents used the
whole 5-hour window in about 15 minutes (26 Sep).
- Craft work in code. The logo kerning on 13 Jun,
which is where your visual-craft STOP rule came from.
- Topics in the wrong place. Now fixed by the WRONG
CONVERSATION banner.
The four things behind the
anger
- “Where is it?” Paths and links, corrected at least
seven times.
- “Why am I waiting?” Silence while Claude works: six
incidents from 14 Jul to 6 Nov.
- “Too much text.” From 15 May to 8 Nov, in both Code
and Cowork.
- “You didn’t check.” On 28 Sep the site was called
fine while big films were missing.
More rules haven’t fixed these. CLAUDE.md is 206 lines and the same
four failures keep coming back. The fixes that held were mechanical
ones, like the timestamp hook.
Your working patterns
- Long sessions on purpose. One session, one arc,
works for you.
- Dictate long, answer short. Numbered questions and
“1y 2y 3n” replies suit you.
- Hand off and walk away. Good for bounded jobs, bad
for open-ended creative ones.
- Frustration becomes a rule within minutes. You
learn fast, but the pile of rules keeps growing.
- Warmth. You’re quick to forgive, and the banter
helps.
- The clock. Messages after 23:00: about 10 a month,
then 21 in August, 42 in September and 120 in October. The tired moments
and the worst outcomes cluster there.
Your system
- Alive: the hooks, todo-php, WhatsApp alerts,
park:, and STATE-OF-PLAY with /handover.
- Faded: the three-tier todo,
/away, the
N-back nudge and PLANNED-UPDATES.
- Too heavy: the STATE-OF-PLAY files run to 1,141
lines (Odeon), 974 (OT48) and 755 (todo-php). Copy stevehomer’s, which
stays at about 100.
- Git: only Odeon really uses it. Nothing from
stevehomer’s news work has ever been committed.
Life, admin and energy
- Jobs that don’t close: the A2 letter (open since at
least 8 Jul), Virgin Media, One Login and the licence, the Thames Water
call, the orthopaedic chase, the U3A emails, and the ADHD follow-up (due
late November).
- The pattern: your system holds these jobs but
doesn’t move them. Each needs one 10-minute first step on a set
day.
- Energy: the building brings you real joy, but the
late nights cost you the next day.
- A gentle note: if low mood ever gets heavy,
Samaritans answer any hour on 116 123.
Flags
- Change your Glow password.
- CallMeBot: your key and phone number are in
transcripts. The risk is low.
- Odeon staging copy:
/odeon/nordic-next/ is waiting on your OK to delete.
- News task: it’s disabled, not deleted.
Three big themes
- You’re a builder who loves building. Draw the
finish line before you start.
- They’re delivery failures, not intelligence ones.
Fix them with hooks and fixed formats, not more rules.
- Energy is your real budget. The late nights are
where both quality and mood leak away.
Loose ends
- Finish: Odeon’s four picks then a freeze, the ASDA
price tracker with the 30 Oct and 6 Nov orders, the Glow password, and
the A2 letter.
- Decide: pause OT48 until spring? Send the Money
plan emails or drop it? Decide on ActivityLogger or retire it? Do the
Cloudflare move (two minutes of clicks)? Push Thames Water or let it
go?
- Drop (with your OK): the bus app, the
aftertheappointment rebuild, the Prime spec, TV films V1 to V3,
/away, the three-tier todo references and the N-back
nudge.
Suggestions
- “Finished when …” as the top line of every
STATE-OF-PLAY.
- A 23:00 “It’s late. Park it?” nudge, built only
with your yes.
- A slimmer CLAUDE.md, about 60 lines with the four
delivery rules on top.
- One 10-minute admin job a day, straight after good
morning.
- STATE-OF-PLAY files under 150 lines.
Questions for you
- Odeon: once the four picks are made, can we call it
finished?
- Late nights: would a 23:00 nudge help you or annoy
you?
- Tuesdays: what happens on them, and is it worth
copying?
- December: which ONE real-life item would make it
feel lighter if closed?
- Chat: shall I merge in the Chat overview when you
have it?
Answer by number, e.g. “1y 2n 3 choir”.