v4 · local-first work graph

What can move now?

Your work already has a shape: issues block issues, PRs wait on plans, notes never reach the tracker. DepViz reads that shape and answers the only three questions that matter at the start of a day.

What can move now? What is blocked? What should happen next?

Open the app Read the source

The app opens on a stateless board — hit Load sample to see the graph with data. Sign in with GitHub only when you want to sync a real board.

Ingest

GitHub issues, PRs and Projects sync in. Local-only note cards and manual dependency edges cover everything the tracker never knew about.

Resolve

Everything lands in one board-scoped graph. Dependencies are computed, not vibed — ready vs. blocked falls out of the edges.

Act

A ready queue, a blocker list, and a morning brief. Create issues, comment, and push changes back to GitHub without leaving the board.

Local-first, boringly

State is a SQLite file. Events are JSONL. The whole engine is a single static Go binary with the web app embedded — no runtime, no cluster, no database to operate.

It runs on your laptop against .depviz/state.db, or as a server like this one. Same binary either way.

Built for agents too

The graph is exportable as JSON and every read has an HTTP endpoint. Coding agents ask DepViz what is unblocked instead of guessing from a flat issue list.

The point of the POC is not a pretty graph. The point is a useful daily answer.

Or stay in the terminal

make install

depviz sync            # pull GitHub issues, PRs, projects
depviz ready           # what can move now
depviz blocked         # what is stuck, and on what
depviz brief           # the morning answer
depviz server          # this web app, locally

Open the board

The live instance is running right here.

Open the app