The board

A local git client scoped to your work, with no build step and no network calls.

lane board opens a local web page. It is a git client scoped to your work, and it replaces reaching for a desktop git app.

It serves only to your own machine and reads the same files the commands do. Nothing is sent anywhere.

Three places

Home is what opens: the work you have in progress, what each piece touches, and what needs attention. Lanes are ordered by what wants a decision, not by name, and each repo shows the next useful action — pull, stage, commit, push, open a pull request, finish.

The board home screen: three active lanes and one parked, across five repos — Three active lanes and one parked. The line at the top answers “what should I do next?”

Work is one piece of work: the repos it spans, the files you have changed, the diff of the one you picked, and a commit box. Side panels cover History, Notes, Refs, Spec and past Sessions.

The board showing an unstaged diff in the api repo, with worker and billing-core in tabs — Every repo of the lane is a tab. Staging is per file, and the commit box counts the subject line for you.

History has a scope toggle: this repo’s branch, or every repo of the lane at once. A piece of work spans repos, so its history should too.

The board's history view with commits from worker, billing-core and api in one timeline — Commits from three repos interleaved into one timeline, each tagged with where it came from.

Memory browses the four scopes and what is in each, flags duplicates, and lets you re-scope a memory that was filed in the wrong place.

The board's memory browser showing scopes and one memory with its reasoning — Each memory carries its **why** and **how to apply**, so a fact that turns out to be wrong can be argued with.

Press the jump control in the top bar, or Command-K, to move between pieces of work without going back Home.

Notes

Ticket keys link wherever tracker.url in registry/config.yml points. Blank means keys show as plain text.

Secret files are never shown: the server drops them by path before git is asked for any content.

The page is plain HTML, CSS and JavaScript with no build step, and makes no network calls beyond its own server.