Switchboard is a Go daemon that finds each running coding-agent session on my desktop, works out its terminal window, and publishes a status file. The status bar shows one chip per session, and clicking it jumps there.

• A once-a-second scan of /proc is the source of truth, so sessions need no registration. Claude Code hooks add status color, and the daemon works without them.
• The process-to-window join spans process table, terminal multiplexer, and compositor, anchored on the controlling TTY, and fails closed on zero or multiple matches.
• Death detection uses pidfd_open and poll, backed by a reconciler sweep because a restart orphans the pidfds. Both were agent proposals I approved.
• I had the Bash/Lua prototype rebuilt in Go after reading its single-writer FIFO daemon as a mutex reimplemented in shell.
• CI runs go test -race on amd64 and arm64, and the deploy script rolls back unless the running process reports the intended revision.

Linux only, one user, running daily as a systemd unit.

Lysilogy points at a folder of scientific PDFs. A Rust backend extracts each with Poppler, shells out to a local coding-agent CLI for a typed analysis, and serves a keyboard-driven React reader with four levels: Abstract, Overview, Glossary, Text.

• A model-proposed quotation becomes a highlight only if it is located in the PDF’s word geometry. Ambiguous or missing matches yield no highlight.
• A source note is shown only if every URL it cites resolves.
• One outbound-fetch gate serves model-cited and user-pasted URLs. It rejects private and reserved addresses and walks redirects manually.
• A blind A/B lane tests prompt changes against a promotion rule I specified before any data existed. The tested treatment was not promoted.

Taskbuffer collects the checkbox tasks in my markdown notes into one Neovim buffer, sorted into horizons from Overdue to Someday, and edits the source notes in place. It is pure Lua with no build step and depends only on ripgrep. I use it daily.

I hand-wrote the first two versions, about ninety lines of Bash and a 62-line Go filter in a separate repo, and coding agents under my direction wrote all of taskbuffer.nvim, Go version included, and the Obsidian port.

• It began as a Bash script, with a small Go program taking over date bucketing when the vault grew.
• The first plugin version required a Go toolchain and a build step on the user’s machine, so I had agents rebuild it in pure Lua.
• The Lua cutover ran behind a flag, gated on parity with the Go binary it replaced.
• A TypeScript port for Obsidian drives the same notes from my phone, held in parity by a written contract and a ported test corpus.

Keyboard Calendar is a fork of the Obsidian Full Calendar plugin, cut down to one model: a single local folder of event notes, each a markdown file with a date, start, and end in its frontmatter, rendered by FullCalendar in month, week, and day views. It runs on desktop and phone.

The TypeScript was written by coding agents under my direction and review.

• The calendar is modal. Normal mode moves between events with h, j, k, l and counts, grab mode slides an event in 15-minute steps, scale mode stretches its end, and a blockwise insert mode drafts a new event from a quarter-hour cell. Moves and scales undo and redo.
• Edits preserve unrelated frontmatter and the note body. Weekly recurrence keeps local wall-clock time across daylight saving changes, and omitted occurrences are recorded in the note.
• The cut removed the Google and CalDAV connectors, the React event editor, and events stored in daily notes, in phases that each left the plugin buildable, tested, and revertible.
• On narrow screens the week keeps all seven days and scrolls horizontally, with a fixed day view in the mobile drawer.

Vim Map is a fork of Map View, the Obsidian plugin that places a vault’s geolocated notes on an interactive map. The fork adds a modal, keyboard-first way to drive the map and a layer system for boundary regions kept in notes.

The TypeScript was written by coding agents under my direction and review. All 29 fork commits carry an agent co-author trailer.

• A normal mode for the map, with a mode badge, a command that focuses the map, vim-like keys for panning, zooming, and moving between markers, and a go-to place finder on Shift+G.
• Boundary layers: GeoJSON regions stored in notes, with per-note color, per-level hover panes, nested regions, and a layers toggle in the map controls. Regions inherit their note’s tags, so tag queries match them.
• Keyboard interaction degrades gracefully on mobile, where the plugin also runs.
• A deviations file catalogs every place the fork departs from upstream.

One repository holds my editor, shell, window-manager, and tooling configuration, plus setup scripts that bring a fresh machine to a working development environment.

• The Neovim configuration is in Lua, built out through 2024 as my daily work moved into the terminal.
• Terminal, shell, and window-manager configuration for a Linux desktop is kept alongside it.
• Setup scripts take a bare install to the full environment.

Each day is one plain-text .retend file of 96 lines, one per quarter hour, and the whole record is greppable. Running retend opens today’s file in Neovim with the cursor on the current quarter hour, and I write down what I did after the fact.

• Two designs were discarded, a Google Calendar log in late 2022 and a Neo4j and Java application, before the plain-text format in early 2023.
• A line’s position is its timestamp, so lines carry no time and the file needs no parser.
• The review tooling is a catch-up mode opening the last week in splits, a ripgrep audit for unfilled days, and per-category rollups over date ranges.
• A small Go exporter from late 2024 coalesces consecutive quarter hours in the same category into blocks and emits ICS.