See where agents write your code, and what it costs you.

Agent City turns a git repository into a 3D city. Files are buildings, folders are districts, height is how often a file changes. It shows where to review harder, what keeps getting reworked, where tests are missing, what only one person knows, and what changed since your team started using coding agents.

npx github:al-ex-ai/AgentCity .

Runs on your machine and opens the city in your browser. Nothing is uploaded. Works on any git repository; agent records from Claude Code, Copilot, Cursor, Aider, Devin and git-ai add the agent view.

What it answers

Where do we need stricter review? Large files that change often, weighted by agent share when records exist.
What keeps getting reworked? Files that need follow-up commits within 48 hours, overall and after agent changes.
Where is the verifier missing? Source files that change while their tests never do.
What does only one person know? Code with a single author, or written by agents with one human.
What changed since agents arrived? Pace, change size, follow-ups and test habits before and after the first agent instruction file.

Already have a city.json?

Open it here, or drop it anywhere on the page. The viewer runs in your browser.

Open city.json

Open source, MIT license. Source on GitHub · Built by Alex Husniddinov

See where agents write your code, and what it costs you.

Explore an example

What it answers

Already have a city.json?