• What it is. A lightweight Go daemon that automatically discovers every Claude Code session running across your terminals and windows, shows each one’s live status — working, idle, or waiting for input — and lets you switch to any of them from a status-bar chip.
• Why it matters. When you run many AI agents at once it’s easy to lose track of which one needs attention. Switchboard turns a scattered set of sessions into one glanceable, clickable list, with zero configuration.

Technical details

Direction mine: the Go implementation was built by AI coding agents, with design calls I reviewed and approved. The original Bash/Lua prototype was hand-written.

• Directed the daemon design: it correlates each Claude process across three namespaces that share no common identifier (/proc, wezterm, Hyprland), anchoring the join on the kernel-owned controlling terminal as the one match key that cannot drift
• Approved death detection built on pidfd_open(2) and poll instead of polling or signals — the chip vanishes the instant the kernel marks the process a zombie, however it died (Ctrl+C, /exit, kill, OOM, parent shell death)
• Directed discovery-as-source-of-truth: sessions need no naming, tagging, or registration, and Claude hooks are pure enrichment that degrade gracefully to working/idle/permission status colors
• Directed the multiplexing of four signal sources — a 1 Hz /proc scan, the Hyprland socket2 event stream, a 5 s reconciler, and a Unix-socket RPC server — through a single write-locked store with atomic-rename JSON persistence
• Directed a rewrite from a ~25-file Bash/Lua prototype I had hand-written: a FIFO single-writer daemon built to serialize state writes collapsed into one sync.Mutex, eliminating a whole class of state-corruption bugs

• What it is. A Neovim plugin that scans your plain-text markdown files, pulls out every task — checkboxes, dates, tags, durations — and collects them into a single buffer grouped by when they’re due (Overdue, Today, This Week). You can complete, defer, or time tasks right from that view.
• Why it matters. Notes accumulate to-dos everywhere. This brings them together without leaving the editor or adopting a separate task app, so your tasks stay in plain text you own.

Technical details

• Built the tool first as Bash scripts, then as a compiled Go binary behind a Neovim Lua UI — a config-driven Go parsing engine (regex generated from user config; checkboxes, dates, tags, durations, markers), ripgrep-backed recursive scanning, and output formatted into time-bucketed horizons (Overdue, Today, This Week)
• Implemented in-place file mutation for task state changes (defer, complete, mark irrelevant) with marker tracking and timer start/stop/complete workflows, plus multiplatform test coverage in Docker and GitHub Actions CI
• Directed AI coding agents to rewrite the plugin to pure Lua, dropping the Go build step so the current taskbuffer.nvim installs with zero external binary
• Directed a TypeScript port (obsidian-taskbuffer) bringing the same plain-text task workflow to Obsidian

• What it is. A single repository holding my editor, shell, window-manager, and tooling configuration, plus setup scripts that bring a fresh machine to a fully working development environment.
• Why it matters. It makes my setup reproducible and portable — a new machine is productive in minutes, and every change to how I work is tracked, reversible, and documented.