📈 GH Trending Explorer 🎲 Surprise me

← all repos

ymatrix1 / vantage

git clone https://github.com/ymatrix1/vantage.git v0.2.0 · 5d ago

A calm, visual view of the true state of your AI-assisted work. Tracks work items from Asked to Verified on evidence, not agent claims, across Claude Code, Codex, git and PRs. Local-first.

—
stars, 24h
+31
stars, 7 days · #1,284
+31
stars, 30 days · #8,663
31
★ total · +31% this week
0
forks · 1 open issues

Star history starts 2026-10-20; the chart appears after the second daily snapshot.

LanguageTypeScript
License—
Created2026-10-14 (6d ago)
Last push5d ago
Watchers0
OwnerUser

GitHub topics

Links

README excerpt
# Vantage
## What is Vantage? (60 seconds)
Vantage runs on your own computer and shows how far each piece of your work has *really* got. When AI coding agents do much of the typing, it is easy to lose track of what was asked, what was built and what was actually tested. Vantage reads the traces your agents and git leave behind and draws one row per piece of work. A row moves forward only on evidence, such as a test that ran after the last edit. What an agent *says* never moves it. Nothing leaves your machine.
One example item, "add a retry to the uploader", moving along the track:
 [code] 
It sits at **Built · no proof yet** until a real test runs after the last edit; then the third dot fills in. New here? Read the plain-language guide, or run `vantage tour`, a guided, offline walkthrough (`vantage tour --demo` opens made-up data you can click around; see first run).
**Learn more**
| You are | Start here |
|---|---|
| A new user | Guide, then the glossary (in Portuguese: Guia, Glossário) |
| A contributor | AGENTS.md, architecture, the specs |
| An agent installing it | Install guide for agents |
| Curious about the method | A2V: Asked to Verified |
All docs by audience: docs/README.md.
A personal, calm view of the true state of your work across AI coding agents, git, pull requests, CI/CD, monitoring, Jira or Linear, and Slack.
Vantage tracks **work items**, not sessions. Each item moves along one evidence-based track, the **A2V track** from the A2V: Asked to Verified method:
 [code] 
A card moves only on evidence: a git diff, a test or data check that ran after the last edit, a PR approval, a deploy, a clean monitoring window. What an agent *says* never moves a card.
## Status
**Phase 1 (the first usable slice) is built** for Claude Code and git: hook capture into a local spool, a SQLite store, the git scanner, the linker, the stage machine (Asked, Built, Proven), a `Stop` hook gate in warn mode, a terminal status line, a secured local Track page, a one-process daemon, and the installer. It has not been used day to day for a week yet (the Phase 1 exit, see the roadmap), and there is no published release yet (the release pipeline is built, see RELEASING.md). Reviewed, Shipped and Verified need sources from later phases.
Tested in CI on Windows and Ubuntu. Developed and run by hand on Windows first.
## Install
**Recommended: let Claude Code do it.** Open Claude Code in the repo you want to track and paste this:
 [code] 
The agent follows the install guide and stops at anything that fails. You stay in control at two points:
1. **Before anything changes**, it shows you `vantage add --dry-run`: the exact files it would touch, nothing written. It waits for your explicit yes.
2. **After the yes**, it installs (with a backup of your Claude Code `settings.json`), starts the daemon, runs `vantage doctor`, and tells you how to open the Track page.
It never adds tokens or credentials, never commits anything, and never edits your settings by hand: only `vant