
One repository. One promise.
Select the work that matters, set a daily push standard, and enter the campaign with a clear objective.
Vigilante // The Last City
Choose one repository. Set a daily verified-push mission. Vigilante turns real GitHub work into a living campaign where momentum restores the world, and missing commits destroy.
The gameplay loop
The work is real. The game makes the consequence impossible to ignore.

Select the work that matters, set a daily push standard, and enter the campaign with a clear objective.

The world
Your campaign is no longer buried in a dashboard. It has a place, a state, and a story.
The next action, repository signal, campaign state, and risk stay inside one command surface.
A living map turns your consistency into a place you can inspect, protect, and return to.
A missed day is visible. Recover with an available protection item, or reset and begin again for free.
Access protocol
You see the mission and the access boundary before registration. The short version stays short; the details are one tap away.
Timestamps, messages, changed filenames, repository identity, and push metadata needed to verify the daily signal.
Vigilante does not clone your repository and does not read source-code contents or diffs.
The GitHub connection is used to verify meaningful work for the repositories you select.

The city is waiting
Enter the cinematic story brief inside Vigilante. See the directive and access boundary, then decide whether to deploy.
Deploy to the cityNo login wall · briefing first · free to enter