Terminal recordings
What goes on in my console: at the top, the working session as it was last night; further down, the sessions behind the articles, replayable in the browser. Most are condensed reconstructions of a Claude Code session, taken from its real transcript; others are real captures of the console or of the site chat. Each one says plainly what it is.
In the console right now
Every window of my tmux session, and what I did in it with Claude Code, day by day: what I am working on this week, and what may become an article. The summaries are in French. Click a window in the bottom bar to browse it.
✔ Redone every night from the real conversations, with no human review. The lab's model summarizes each day from a conversation that is already sanitized: hostnames, addresses and domains replaced with fictional values, tool calls without their output, and any passage a guard flags removed before the summary. The summary then goes through the same guards (allowlist, denylist of the real inventory, review by the model) and is removed if it trips one.
Loading the snapshot…
The recordings
- The clock in the prompt, for realThe same prompt sent three times in a row to Bob's model, a Qwen3.8-27B served by Ollama, with the time to the second placed in three spots: at the top of the system prompt, at its end, then inside the question. llama-server's log says how many tokens it had to read again each time: 3,483, then 1,024, then 29.
- The reply that left by the wrong leg, for realThe frozen SSH failure, replayed for real and captured as is: rule 102 removed from a host with two legs, a session from the Mac that goes quiet for 40 seconds and never comes back while pfSense's state melts from 30 seconds to zero, then the rule put back and the same session getting through, with a state kept for 24 hours.
- Three cards, two brainsTwo sessions around Bob's voice: the evening it moves to the 27-billion-parameter dense model, set up from a phone, then the prefix measurement that showed where a clock belongs in a cached prompt, and what the agent had misunderstood the first time.
- The back doorTwo days on hosts with two legs that answer through the wrong one: the failure reproduced from cloud-01, three source-routing rules tried by hand and then declared in a NixOS module, an SSH freeze the agent had wrongly set aside, and the container whose reply took the one path the rules could not see.
- The check that refuses to publish, for realThe same net as in the reconstruction, replayed for real on a copy of the repository: a clean pass, a domain planted in a DNS zone, the hard refusal, a one-line fix, and the proof in the sanitized tree.
- The night pipeline that liedA day on the night pipeline, and three green statuses that said “all good” for reasons unrelated to the work: a stale copy that succeeded, an API refusal read as agreement, a shell that exited zero without running anything.
- Bob looks up the movie timesThe voice assistant gets a web search, answers correctly one evening, then makes up showtimes two days later. The fix is not a better search: it is going to the source for the schedule.
- The liars' benchA false sentence planted in the architecture drawing, then the same case in Qwen Code with two models: the basement one reads part of the data and declares nothing changed; qwen3.8-flash goes to read the WireGuard peer configuration and corrects the sentence. The small model of the 3.8 generation scored fifteen out of fifteen, like Opus 5.
- The cluster picks up the cardsAn idle GTX 960 handed to Kubernetes: the driver on the host freezes the kernel without ever saying “graphics card”, the driver moves into a VM, a bisect blames the wrong suspect, and the card-swap cycle, replayed live, flushes out four bugs.
- The cheapest cousinThe night pipeline that redraws the architecture page leaves Opus and the subscription for qwen3.8-flash, in Qwen Code, on Alibaba Cloud. Guard-rails laid before the first try, the wrong culprit named, a decision taken in Ludo's place, and a first night stopped at the fiftieth turn.
- Bob finally reads his own articlesThe evening the site's chat went from a catalogue of titles to the content of its articles: a bge-m3 semantic index with no database, then four failures in a row — a 404 frozen at the edge, an HTTP 500 on a second system message, a bot announcing its own disappearance, and a fix that never reached production.
- GPU on demandThe day the second gaming station gets its graphics card: a clean three-file change, then three failures that each look like something else. Asymmetric routing, a card that does not come back from a shutdown, and an “unreachable” VM that was simply paused.
- An invisible BIOS, driven blindA BIOS screen nobody can see, arrow keys that never arrived, a wrong turn into the wrong firmware — and a machine recovered without ever seeing the screen.
- A smart-home button that hires a ClaudeA Home Assistant button that opens a tmux window with a fresh Claude Code session, drivable from the phone while it lives. Plus the two-tmux-servers trap.
- The survivor island, unplugged for realThe lab's last pull-the-plug test: the cord pulled, the shutdown cascade firing on the UPS's signal, a BMC lost on the wrong VLAN, and the latch closing out the outage by itself.
- The pipeline presses applyOne tool picked per repo, a destroy gate tested against a real DNS record, then the same merge delivered on the NixOS side by comin, with nobody at the keyboard.
- Unplugging the NAS for scienceThree deliberate power cuts to the NAS to verify freshly written liveness probes. Each cut finds something the previous one had missed — and the last one is boring, which was the goal.
- Breaking your own etcd quorumThe same command, twice. The first time it is safe, the second time it takes the cluster down — because the number of voters changed in between.
- NFS to SSD migration, driven from the browserClaude in Chrome configures the NAS while I watch: a volume to create, a share to rename, permissions to fix. And three hard stops where the agent hands control back.
- The check that refuses to publishThe last net before a repository goes public: a forgotten domain, a hard refusal, and the fix added on both sides.
- Converting one node to NixOSA machine reinstalled over SSH, with no screen and no USB stick. Secure Boot and an oversized initrd are the real obstacles.