Skip to main content
Live GitHub accountability game

Vigilante // The Last City

Your code keeps the city alive.

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.

No credit card No source-code contents Built for solo developers

The gameplay loop

Ship code. Hold the city.

The work is real. The game makes the consequence impossible to ignore.

Directive loaded

One repository. One promise.

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

Dream City game map

The world

Welcome to Dream City.

Your campaign is no longer buried in a dashboard. It has a place, a state, and a story.

Mission Control

The next action, repository signal, campaign state, and risk stay inside one command surface.

Dream City

A living map turns your consistency into a place you can inspect, protect, and return to.

Recovery protocol

A missed day is visible. Recover with an available protection item, or reset and begin again for free.

Access protocol

Trust is part of the interface.

You see the mission and the access boundary before registration. The short version stays short; the details are one tap away.

Commit metadata

Timestamps, messages, changed filenames, repository identity, and push metadata needed to verify the daily signal.

No source contents

Vigilante does not clone your repository and does not read source-code contents or diffs.

Purpose-limited access

The GitHub connection is used to verify meaningful work for the repositories you select.

The Last City at night

The city is waiting

Will your code
keep it alive?

Enter the cinematic story brief inside Vigilante. See the directive and access boundary, then decide whether to deploy.

Deploy to the city

No login wall · briefing first · free to enter