Every session begins from nothing.
What the project is. What was decided last week. What already failed. You retype it, or you lose it, and most of the effort goes here, before any work happens.
an empty prompt →“Write this up as a one-page HTML brief.”
You did not list the specifications, because you have listed them before. One page. One accent colour. System font. No inner scrollbars. One self-contained file that opens with no network. All of it is already on your desk, so it goes and gets it.
the tools fire →The right four notes light up.
184 notes, 988 links. You never search it. The question walks the graph and the handful that matter come back, including the one that cost an hour three weeks ago.
watch them recall →Three tasks, spoken.
Hold the mic and talk. Local Whisper turns it into text on your machine, no upload, no cost. Tick them all and hand the lot to Claude as one plan.
push to Claude →Green means finished. It still waits for you.
Work comes back marked in review, never silently closed. Nothing moves to Completed until you say so, the board is a record you can trust because you signed each line.
awaiting approval →The limit arrives. It taps you, once.
The session window is nearly spent. One tap on remind me at reset arms a local timer against the reset time, and at 3am the desk taps you, so the next window starts because you chose it, not because you happened to look.
arm it, then watch it fire →It asks what it should have learned.
At the end of the day it proposes the lessons worth keeping, you confirm or reject each one. Confirmed, they go into the skill files, and the next run inherits them.
confirm the lesson →The next page costs four questions less.
The skill you confirmed last night is a file on your disk now. Tonight you ask for another page, the terminal reads that file before it writes a line, and every specification is already applied. You never restate them, because they no longer live in your head.
watch it get pulled →Do the job once, out loud.
You export a report from a spreadsheet every Monday and you have never written it down. So do it once while the owl watches: it records the screen, hears what you say, and turns the two into steps. Your own Claude drafts the skill from that, and nothing is saved until you approve it.
record, merge, approve →It tells you where it hurts, and what to do.
The Nest is the morning view, and the Pulse behind it is the honest one: four vitals, every long-lived process against a written budget, and the moments it struggled marked in red. Click a red mark and it says what happened, why, whether it recovered, and what to change next time.
open the red mark →Where the day actually went.
Sessions, prompts and shipped work laid on one timeline, including the gaps. That 90-minute hole at two o’clock was a meeting, and it still needs clocking.
find the gap →The whole day, in one sentence.
The same record at three depths: every thread point by point, then just the headlines, then a single line under two hundred characters, the one you actually paste into a status update.
watch it compress →
Owlwaysa way forward
4 recalled. The question walked the graph, you never typed a keyword.
Nothing moves to Completed on its own. Green means Claude is finished, the board still waits for you.
- You arm it. One tap on remind me at reset. That chip is the whole setting, no dialog, no preferences page.
- The desk keeps the reset time. It already reads your own usage window, so it knows the session rolls over at 3:00am.
- A local timer waits. Nothing polls, nothing is sent anywhere. The countdown lives on this laptop and survives a restart.
- At the reset it taps you once. A single desktop notification, and the same line on your phone if that channel is switched on.
- Then it disarms itself. The chip drops back to unarmed. One reminder per window, so it can never nag you twice.
No model is called to do any of this. A clock and a notification are not intelligence, and the cheapest feature in the app is the one that stops you burning a window you did not know had reset.
Anything you send is one self-contained page, one accent colour, system font, and no scrolling inside cards.
Never pull a font or a chart library off a CDN, the file has to open with no network, on a laptop on a plane.
✓ 2 lessons written into 2 skills
The first spec went into the skill you already had. The second was general enough to be its own, so one-page-html now exists, and every future page inherits it.
Last night’s lesson, spent this evening. The skill is a plain text file, you can open it, edit a spec, or delete the lesson if it turns out to be wrong.
The owl watches and listens. Teach it a skill by doing a job once, all on this Mac, zero tokens.
Four steps and one gotcha, drafted from what you did and said. Nothing is written until you say so.
You never wrote a procedure, the gotcha you muttered halfway through is the part a written SOP always loses.
Good morning. Thursday 10 September
Every number here is measured on this Mac, and the remedy is a shell command you can read. Nothing was sent anywhere to work out that the fans were losing.
Every red dot is a moment it struggled. Click one and it tells you what happened, and what to change.
hot, sustained load building up
- 📋 what happened
- Spiked to 76.9°C and held there for 3 minutes.
- 🔍 why
- Ran hot with two back-to-back builds and the security scanner at 43% as the biggest load at that moment, short heat bursts under real work are by design.
- ✅ resolution
- Recovered in 3 minutes, back to 69.5°C. No hand needed.
- 🛡 next time
- Keep the vents clear and off soft surfaces; give back-to-back builds a cooling gap, sustained heat is what throttles, not the spike.
39MB past its written budget, swap at 82%
- 🔧 remedy applied · automatic
- shed-ollama unpinned the idle embedding model and handed 353MB back, backend settled to 104MB, swap to 41%.
brief-writerplain-speak
unclocked
brief-writerinformation-density
eod-wrapup
14:00–15:30 has no prompts and no file changes, but your calendar had a call. It is the only thing today that is not accounted for.
Detailed Work Summary, Wednesday 9 September
- Built it as one self-contained page against the usual specs, none of which had to be restated, because they were already on the desk.
- Added a summary box at the top and re-cut two sections to hold it on one page, rather than letting the middle scroll.
- Swapped the accent to the agreed blue and sent it round ahead of Thursday’s call.
- Two specifications confirmed: one self-contained file for anything you send, and a system font stack rather than a webfont, the second was general enough to become its own skill, one-page-html.
- A 90-minute hole at 14:00 with no prompts against it, almost certainly the call that overran, still to be clocked.