Check Code Graph Freshness with vg status
vg status reports graph freshness, node and edge counts, staleness, and resolver rungs, comparing the committed graph against your working tree so you know when to rebuild.
Stale graphs give stale answers. vg status tells you whether your code graph is current: it reports freshness, node and edge counts, staleness, and the resolver rungs used, comparing the committed graph against your working tree.
Prerequisites
- A built code graph from
vg build
Steps
1. Build the graph
vg build
2. Check status
vg status
3. Read freshness and staleness
The output shows node and edge counts (the size of your graph), staleness (how far the graph has drifted from the current code), and the resolver rungs used to build edges. It compares the committed graph against your working tree, so you can see exactly what is out of date.
4. Rebuild when stale
If vg status reports staleness, refresh the graph:
vg build
The incremental build only reprocesses what changed.
5. Confirm sync
Run status again to confirm the graph now matches your working tree:
vg status
Verification
After vg build, vg status should report the graph as fresh with no staleness against the working tree, and non-zero node and edge counts.
Next Steps
- Rebuild incrementally with
vg build - Make the graph committable with
vg share - Explain a node with
vg show