01:41 — 9 November 2026
An overview of Steve’s work in Claude Code and Cowork, written overnight on 9 November 2026. Honest and kind, as asked.
C:\Users\steve\Herd\steve\overview-brief-for-chat-cowork.md.A:\projects\to-query\steve_profile_03.md.Six Sonnet agents each read one theme in full and wrote a report. I
cross-checked them and wrote this. Their reports are full of dates and
quotes, and they are kept in
C:\Users\steve\Herd\steve\overview-2026-11-sources\.
| Month | Messages | After 23:00 | Main focus |
|---|---|---|---|
| May | 466 | 10 | New NVMe drive, OT48 “cousin mission”, Odeon rebuild starts, Polaris, first news page, bus app |
| Jun | 608 | 10 | OT48 brand and site redesign, ASDA picker, GPU blank-screen fix, Odeon “finally there” (12 Jun) |
| Jul | 454 | 8 | todo-php built (8 Jul), ActivityLogger, BIOS and wake fixes, the big July tidy |
| Aug | 504 | 21 | Hardware central restarted, Odeon Gantt idea, phone and Tasker, good-morning routine |
| Sep | 389 | 42 | Odeon git era and code reviews, sound problems, OT48 strategy then on hold |
| Oct | 581 | 120 | Odeon Nordic redesign live (29 Oct), WhatsApp alerts, CLAUDE.md rewrite, ASDA price tracker, news globe |
| Nov (to 9th) | 189 | 13 | News specials then cancelled, phone tabs cleared, utilities monitor |
| Project | State on 9 Nov | One honest line |
|---|---|---|
| Odeon | Live at v9, good on phone and PC | Did its main job by June; needs four picks, then a freeze |
| OT48 | Site built and secured; business on hold | Zero outside customers; it’s waiting on Oregon, not on code |
| ASDA | Works; you drive the tick page yourself | Best when you hold the logic and Claude does the legwork |
| todo-php | Used daily via the session-start block | Your most-used tool, and also the one you over-build |
| Morning news | Automatic run cancelled 8 Nov | It grew until it became a chore; stopping was right |
| Hardware | Mostly settled | Big wins; audio and the Wi-Fi errors are still open |
| Phone, tabs, comms | Tabs cleared 5 Nov; WhatsApp alerts working | The WhatsApp alert is the cleanest success of the six months |
| Utilities monitor | Started 8 Nov | Blocked on the British Gas login |
| Mail triage (Cowork) | Rolling, every few days | Quietly very useful: it found a forgotten £150 energy card |
| Thames Water (Cowork) | Unsolved | Charts and letters done; the cause is still unknown |
| Money plan | Untouched since 9 Jun | Three “send-ready” U3A emails never sent |
| ActivityLogger | Untouched since 13 Jul | Four decisions waiting on you |
| Smaller ones | Bus app, aftertheappointment, TV films, Prime spec | Mostly parked mid-flight |
What it is. Your private cinema site at https://www.perfectportals.com/odeon/. A scraper on this PC reads the Orpington (and Leicester Square) Odeon showings, and Listings, Double Bills and Gantt pages show them your way.
What got done. Must See stars, Going and Booked badges, saved slots, notes, film cards with scores and trailers, time corrections, failure alerts, two code reviews, git, backups, and the Nordic redesign live on 29 Oct.
Where it stands. On 6 Nov you said it “all looks good ph and pc”. Four choices still sit open: a Labels look, a Films option, a Gantt Bars option, and whether to keep the Samples tick.
Honest line. It was “finally there” on 12 June. Since then every answered question has spawned three more, and on 20 Sept you said “I do feel I am over complicating things”. It’s a lovely, used tool, and it is at risk of becoming a forever-project.
What it is. “Outside the 48”, a US parcel-forwarding service for people in Hawaii, Alaska and the territories. Agna leads the business, and her cousin in Oregon would do the packing.
What got done. A live site at https://ot48.com with customer, admin and warehouse sections, tours, a working ZIP eligibility checker, a strong brand, a business case for Agna, visitor reports, a Grafana dashboard and a September security clean-up.
Where it stands. The 26 Sep review found zero real outside customers. Oregon is on hold because the cousin is unwell, and the rule is not to nudge Agna. The site is ready; the business is waiting on life, not on code.
What it is. Your grocery helper. Claude logs each order from the Gmail receipts, builds a tick page at https://perfectportals.com/asda/, and produces best-before lists after delivery.
What got done. About 38 orders and 201 items logged. The six-tier tick page you run yourself (from 5 Sep). Best-before lists in a settled format. A price tracker (from 23 Oct).
The lesson. Claude’s prediction model kept dropping things you always buy (23 Jun, 1 Jul). On 5 Sep you said “I am reclaiming a lot of this process”, and it has worked better since.
What it is. Your PHP task and chores app (Big TODO v6), with scores, topics, repeat chores and a session-start brief that prints in every Claude session.
What got done. Built from 8 Jul, and it’s the one todo system out of five that is still alive. The calendar picker on 6 Nov was “pretty excellent now”.
Honest line. On 8 Jul you set limits: nothing new for three days, then at most two 20-minute sessions a day. They haven’t held, and the STATE-OF-PLAY file is 755 lines. You said it yourself: “enjoying creating functionality rather than using it”.
What it is. A daily news page on stevehomer.com that grew into a multi-agent morning run, with a press-freedom globe, US midterms and markets specials, and WhatsApp pings.
Where it stands. You cancelled the automatic run on 8 Nov: “every day I’m rushing in here desperate to stop you”. The scheduled task is disabled, not deleted. That was a good decision.
What got done. The second NVMe (A: drive) went in after the missing-screw saga in May. The June blank-screen GPU crisis was fixed: 493 events on 13 Jun, zero by 16 Jun. You also got the slow shutdown cured, the mystery wake-ups found (wake timers, VLC, the HP WakeToRun task), and a BIOS update, the Everything search tool and the Windows-MCP connection all sorted.
Still open. Monitor audio (last seen unresolved 19 Sep), the Killer Wi-Fi PCIe errors, the slow H: drive, the Chromebit, and the local-AI GPU idea.
What got done. The phone’s notification noises were cured (31 Oct). Hundreds of Chrome tabs were exported and cleared (5 Nov). Twilio texting turned out to work after “three months of worry” (30 Aug). The CallMeBot WhatsApp alert has been working since 11 Oct, with 52 messages sent so far.
Mail triage (16 May to 5 Nov). One rolling session: you say “update pls” and get a prioritised action sheet. It found a forgotten £150 Bromley energy card on 1 Jun. By 5 Nov the mailbox was down to about 42,000 messages.
Thames Water (19 Jun to 26 Oct). Your water use jumped about 50% from November 2025. Charts, back-data and letters to Thames Water and A2Dominion are done, but the cause is still unknown.
How you use Cowork. Code is where you build and ship; Cowork is where you hand over a messy one-off job and let it grind. On 21 Jun Cowork found driver updates that Code had missed.
The best moments all came this way. Examples are the Gantt overlap fix (“100% PERFECT. Pls mark as final”, 25 Sep), the Booked marker, and the staged Odeon clean-up.
You decide fast when you can see three to seven versions side by side. Examples are the Must See levels, warning colour scheme F, the OT48 Alaska page (“LOVELY”) and the eligibility page (“LOVE NO 6”).
Hardware is your best-performing area because the problems have logs and event IDs. The wake-up hunt led to “I never would have found what was causing that wake up if it hadn’t been for you” (4 Jul).
ASDA only settled down once you took the decisions back on 5 Sep. The same shape worked for the price tracker, which was framed as a “very rough first draft”.
WhatsApp alerts, /tellme,
restart-claude.ps1 and the tab clean-up. Each one does one
job and is done.
The session-start todo block, the 25-minute reminder (about 1,300 automatic checks since August), and the Odeon scraper on its schedule. Your own July “survival law” is right: what runs itself lives.
Hardware central and the Cowork mail session both work because you can come back after a week, say “update pls”, and Claude picks up the thread.
Killing /away (“kill this for now”, 17 Jun) and
cancelling the news (8 Nov) were both good calls, and both show you can
pull the brake.
The six Odeon prototypes you came back to on 22 Jun got “Ummmm don’t like any of them”. The first Nordic reskin was “depressing”. Big unattended creative jobs leave you with a pile to digest.
Examples are the ASDA demotions (23 Jun), “Oregon” when Agna was in Maui (6 May), the Agna misreporting (21 to 22 Jun) and the film placed on the wrong day (25 Jun).
The /away desktop chaos (17 Jun), the Tasker stalls (22
Aug), and test clicks that unticked two of your real films (23 Sep).
Six Fable agents filled the context window from 58% to 82% in 8 minutes (12 Jul). Six Opus agents used the whole 5-hour window in about 15 minutes (26 Sep).
Logo kerning across Code, Design and Figma (13 Jun): “a massive amount of wasted time and tokens”. Your visual-craft STOP rule came from this, and it’s a good rule.
Disk drives inside the ASDA chat (7 Jun), OT48 living in the ASDA folder, and Odeon done in the OT48 chat (6 Nov). The new WRONG CONVERSATION banner is the right fix.
Almost every outburst in six months traces to one of four delivery failures. Claude didn’t fail to understand you. It failed to deliver to you.
Paths and links. Corrected at least seven times in memory between April and September, and again in Cowork from May to November. 7 Jun: “HOW MANY TIMES MUST I ASK FOR PROPER ADDRESSES”.
Silence while Claude works, and blockers found late. There were six separate incidents from 14 Jul to 6 Nov, and the strongest language in the record was on 1 Nov.
From “You are getting far too verbose” (15 May) to “one big blob” (8 Nov), in both Code and Cowork. On 16 Oct in Cowork: “I’m loving, absolutely loving this shortened version.”
28 Sep: “not what I pay you for!”, after Claude said the site was fine while big films were missing.
Each failure became a new rule. CLAUDE.md is now 206 lines with about 80 correction memories behind it, and the same four failures still come back. Some rules now pull against each other: for example “ask before ANY edit” against “Not changing them is WRONG!” (6 Aug). The fixes that held were mechanical, like the timestamp hook, not written.
“One session, one arc” works for you. Hardware central and the mail triage prove it. Forks and rewinds keep them trim.
You dictate long messages, then reply “1y 2y 3n”. Numbered questions suit you perfectly.
“BUILD IT WHILE I AM AWAY”, then a coffee or a bath. It works for bounded jobs, and badly for open-ended creative ones.
You choose the model and effort yourself and track the 5-hour and weekly limits closely. Sometimes “tokens to burn” sets off a sprawl, as with the late-October news build.
It’s a strength, because you learn fast. It’s also why the rule pile keeps growing.
“You are so clever, and I love you” (30 Jul). “You are a wonderful computer entity” (26 Oct). You’re quick to forgive, and the banter helps both of us.
park: trigger, and STATE-OF-PLAY with
/handover./away and its idle-task queue: nothing
queued since July._old files.The system holds these beautifully but doesn’t move them. Each one needs a single 10-minute first step on a set day, not a better list.
Your own words over six months: “knackered”, “EXHAUSTED”, “too tired to think”, “running out of steam”. The building gives you real joy, but the late nights cost you the next day.
In September you mentioned in Cowork that low mood has been a long-time companion. I won’t analyse that here. If it ever gets heavy, Samaritans answer any hour on 116 123, and your GP or the ADHD team are good people to tell.
/odeon/nordic-next/ is waiting on your OK to delete.daily-news-8am is switched off, not deleted.You said it first, and the record agrees. It isn’t a fault, but each project needs its finish line drawn before it starts, not after.
They’re about where, wait, length and checking, not intelligence. Those want mechanical fixes such as hooks and fixed formats, not more paragraphs of rules.
The late nights are where both the quality and the mood leak.
/away, the three-tier todo references, and
the N-back nudge.Answer by number, e.g. “1y 2n 3 choir”.
C:\Users\steve\Herd\steve\overview-2026-11.mdC:\Users\steve\Herd\steve\overview-brief-for-chat-cowork.mdC:\Users\steve\Herd\steve\overview-2026-11-sources\