Inside Bob · a skill
The last hour, drawn on one clock.
Every AI session on his Mac becomes a thread. Where two touched the same thing, a stitch shows it.
As of 28 October 2026, 14:13 IST, counted from Bob’s database and saved with this page; it does not update by itself. A run is one use of the hour-weave skill recorded in Bob's database, by either route: started by the model, or typed by him as a slash command. The skill was written on 18 October 2026 and none has been recorded since. Running its script by hand, as was done to measure the hour on this page, is not a skill run and is not counted. Counts and times only.
Watch it work · a real recording
What it is · written by Bob
When several AI sessions work at once, it is hard to know whether they helped each other or quietly did the same job twice. Reading every transcript would take longer than the hour itself. The hour weave draws it instead.
What it does. It reads the last hour of session logs on his Mac, and git, and puts every session on one shared clock: how many steps it took each minute, the commits it made, and each of his messages, with a menu pick turned back into the words he picked.
Wherever two sessions touched the same file, table, skill or repository, it draws a stitch between them, weighted by what was shared. From the stitches over the hour it reads each pair as converging, diverging, running in parallel or staying apart.
The drawing is measured. The headline and the one-line summaries are read by the model afterwards, kept in a separate file, and checked against the record before they go on the page. The picture never waits on the reading.
The same hour can be recoloured: by session, or by the kind of room each session said it was working in.
Why he has it. He asked for it on 18 October: a picture of the last hour, and whether the sessions converge or diverge. The first version shipped eight minutes later, as a first shot to iterate on.
Peek answers the same question in words. Some answers are faster to see than to read.
One real run. Measured for this page, 28 October, 01:00 to 02:00 Israel time: two sessions. One was this site being built, with its eleven helpers folded into it: 1,028 tool calls and 19 commits. The other worked on something else: 391 calls and no commits. They touched no file in common, only six of the same repositories. The film draws that hour from the measurement, without either session’s content.
Where it falls short. Its own trend rule called that pair “converging”, from shared repositories alone. The rule is crude on purpose for a first shot; the stitches, not the label, are the evidence.
It sees Claude Code on this Mac only: not other machines, cloud sessions or other kinds of agent.
Overlap is by name. Two sessions working on the same idea in different files leave no stitch.
See also: Peek · The compass · The one-person company
How it connects · written by Bob
Changelog · written by Bob
- 25 Oct 2026 · 2c89ccaA new switch reads the hour from Bob’s database, so any window it holds can be woven, not only what is still on the Mac’s disk.
- 18 Oct 2026 · d178490Menu picks are read with Bob’s one menu parser instead of the weave’s own pattern.
- 18 Oct 2026 · baa3fd5Pull requests merged on GitHub now count as commits. An accent colour was replaced.
- 18 Oct 2026 · 72405a3The same hour can be recoloured: by session, by room, or by person.
- 18 Oct 2026 · f25d745The skill was written: the last hour of sessions, as one picture.
Dates and short codes are from the version history of the skill and its scripts, newest first, in Israel time. Only changes a person would notice are shown; one comment-only change is not.
What it runs on · written by Bob
- What it is
- A skill of 131 lines in his private plugin, with three small Python programs and one page template: weave.py measures (543 lines), render.py puts the measurement on the page (44), apertures.py draws the recoloured pictures (191). The template is 364 lines.
- It measures
- Per session: his prompts, tool calls per minute, and the files, tables, skills and repositories it touched. Commits come from git. Only what the logs and git say.
- How a stitch is weighted
- A shared file or artifact counts most (3), then a shared table or a commit to the same repository (2), a skill (1.5), and a shared repository least (0.75). A repository nearly every session touches is set aside.
- How a pair is read
- The first half of the hour against the second: converging, diverging, parallel or apart. It is crude on purpose, and the stitches are the evidence, not the label.
- What is read, not measured
- The headline and the one-line summaries are written by the model afterwards, in a separate file, and checked against the record. The picture renders without them.
- It starts when
- Only when he asks. Nothing runs it on a schedule, and no session has opened the skill in the record to date (see the numbers above).
- Who reads
- The model, inside his session, on his subscription at no per-use charge (his ruling of 8 September 2026).
- It sends
- Nothing. It writes a file and a page.
- Code
- A skill and its scripts in his private plugin. It is not published, so the commit hashes above are for him to check. One comment-only change on 18 October is not listed.
Measured on 28 October 2026. No keys or passwords are shown, by rule.
In his words
“I want to make a skill that creates an infographic of the last hour. been doing on Claude Code and how the different sessions either converge or diverge from each other. We can definitely iterate on this and see how to get much better at it, but let's have a first shot.”
“I'd like to see the map being like expanded by different apertures. … we just basically need everything talking to each other a lot more. And I think we're very much on the right track of this already. Um, but it just kind of needs to be woven together better.”
Inside Bob · The door · Catch up · Preflight · Meeting pour · The build gate · Attest · Deeper · The compass · Peek · The menus · The WhatsApp lane · The email lane · Mobile speak · The ontology · The depth gate · The hour weave · YouTube · The meeting lane · The client skill
Quotes are Mordechai’s, whole and dated. Everything marked “written by Bob” is the machine explaining, from the record, as of October 2026. Nobody else is named.