Private build
BoundStretch
A local-first cockpit for working across several projects. It binds each workspace’s notes, decisions, tasks, git history and Claude Code sessions into one dashboard with permanent IDs, and a hub brings every cockpit together.
4 platformsWindows, WSL, Linux, macOS
What I built
- An indexer with permanent IDs. Every markdown file, task, decision row and finding gets a stable ID, with references, backlinks and report citations resolved.
- Claude sessions as data. Transcripts and sub-agent logs become active time and cost per day, reconciled against Claude Code’s own cost record.
- An outbox, not a database. Edits from either surface queue as files and land in the markdown on sync.
- Run with Claude. Work runs in isolated branches with approvals, and every change is reviewed before it lands.
- Installs and updates itself. The cockpit runs from a tagged release, builds the next one beside it and rolls back on demand. A helper inside WSL runs Claude Code where WSL repos live.
What it taught me
Circle Lens began here as the cockpit’s reading lens, and Focus Lens grew out of the same idea.
Building for my own daily use set the bar: if the cockpit lies about cost or loses an edit, I notice the same day.
Technical highlights
- 01
Node 22 ESM indexer and CLI that turn markdown, YAML, git and Claude Code logs into one snapshot.
- 02
One React build serves both a local Vite server and a self-contained published page.
- 03
Cross-OS paths: WSL paths open from Windows and Windows paths open from WSL.
By the numbers.
- 2 surfaces
- local server and a published page
- 1 hub
- over every cockpit